Results for meta-ads

CLI for interacting with the Meta Marketing API

A gem for adding Kaminari collection meta data to your API responses that matches the format that works with Kaminari paginate method.

Provides helpers for easy adding of html meta information to Rails applications. * Easily add default description and keywords meta tags. * Customize meta tags on per-view basis * Add head title tag with breadcrubms * Add page title

De.linque.nt is a tool for making meta-posts to Del.icio.us, the social bookmarking site. The key is that the URL you bookmark is the Del.icio.us URL that is created once you have added the new bookmark. Basically, the new post bookmarks itself.

ActiveRecord extension that turns your models into graph objects. Includes helper methods for adding <meta> tags and the Like Button to your views.

OmniTrack is a production-grade tracking and conversion gem for Ruby on Rails. It supports multiple ad/analytics platforms (Google Ads, GA4, Meta, TikTok, Snapchat) via a clean adapter pattern, works in both full-stack and API-only Rails apps, and provides structured logging, background job support, and an extensible pipeline.

A Rack middleware to make URLs in one-page webapps easier. In a couple of recent projects, I've needed to avoid full page refreshes as much as possible. In the first, I wanted to keep an embedded music player active while the user was browsing. In the second, I just wanted fancier transitions between pages. It's possible to do this in an ad-hoc way, but I very quickly got tired of hacking things together. Enter Onesie. Onesie congealed from these requirements: * I want a one-page web app, * But I want the back button to work, * And I want search engines to still index some stuff, * And I (mostly) don't want to change the way I write a Rails/Sinatra app. If someone visits <tt>http://example.org/meta/contact</tt>, I want them to be redirected to <tt>http://example.org/blah/#/meta/contact</tt>, but after the redirection I still want the original route to be rendered for search engine indexing, etc. When Onesie gets a request, it looks to see if under your preferred one-page app path ("blah" in the example above). If it's not, Onesie sets the current request's path in the session and redirects to your app path. If a request is under the one-page app path, the "real" request's path is retrieved from the session and used for subsequent routing and rendering. This means that, as above, a request for http://example.org/meta/contact Will be redirected to http://example.org/blah/#/meta/contact But still render the correct action in the wrapped app, even though URL fragments aren't passed to the server. This is a terrible explanation. I'll write a sample app or something soon.

No description provided.

No description provided.

No description provided.