More than 10,000 new websites integrate with Facebook every day by using one of their social plugins. However most sites that we see are not taking full advantage of what facebook has to offer. Were you aware of the fact that you can get facebook… Read More »
Few days ago while working on a client’s site, we were asked to code a function that restrict uploads to specified file types only (jpg, gif, png). After looking around the repository and finding nothing that can do this, we decided to create a plugin… Read More »
Everybody knows that internal linking is good for SEO. It is also good for user experience because it helps the user relate to what is being talked about in a specific article. Ever since WordPress 3.1 introduced internal linking, like many others we have found… Read More »
A little over a week ago, WordPress 3.2 was released. In that release, there were some server incompatibility issues with JSON. This is the main reason why this maintenance release came so fast in which the core team has addressed the JSON issue, and made… Read More »
On July 4th, the independence day of United States of America, Matt Mullenweg announced the release of the most anticipated WordPress 3.2 which was named after George Gershwin. You all should have already upgraded by now, but for those of you who were enjoying the… Read More »
You know when you need to show certain WordPress posts based on custom fields? We’ve been there. When we first started with WordPress, seeing any code snippet felt intimidating, especially when all we wanted was to display posts with specific information. But here’s the good… Read More »
Used to store interaction and conversion data for campaigns in conjunction with Revenue Attribution.
1 year
_gat_omTracker*
Set, controlled and used by Google Analytics to collect and store data and then send that data to Google Analytics. OptinMonster provides the name if there is no existing tracker found on that page.
-
omCountdown-{id}-{elementId}
Used for countdown elements {elementId} in campaigns {id} to determine when it should complete.
-
om-{id}-closed / omSlideClosed-{id}
Used specifically with slide-in campaigns {id} to determine if it has been closed or not by a visitor.
30 days
om-success-cookie / omSuccessCookie
Used to determine if a visitor has successfully opted in to any campaign on your site to unlock content when using our Content Locking feature.
365 days
om-success-{id} / omSuccess-{id}
Used to determine if a visitor has successfully opted in to a campaign with the ID of {id} on your site.
365 days
omSeen-{id}
Used to determine if a visitor has been shown a campaign by the slug.
30 days
om-{id}
Used to determine if a visitor has interacted with a campaign ID of {id} on your site.
30 days
_omappvs
Used to determine when a new visitor becomes a returning visitor.