Integrate with Popup Maker for automatic event tracking

Hi,

I’d be really happy to integrate your plugins to Pixel Caffeine! ??

There are two things that you might do, in base of how the features work:

– if they are from the server side: for example, a pixel to fire when a page loads (simple page loading, or after a contact form submit, or stuff like that): in this case, you can use the built-in function aepc_pixel_event_code when you need to fire a pixel. It will queue the pixel to fire and Pixel Caffeine will automatically add it when possible. Here an example of the use of this function:

aepc_pixel_event_code( [
    'event_name' => 'TrialSignup', // required
    'value' => '0.00',
    'currency' => 'USD'
] );

You can see the allowed arguments of this function in the file: pixel-caffeine/includes/functions-helpers.php (there is one one function)

– if they are from JS or AJAX: for example, a pixel to fire when a send is successful via AJAX, or when a JS event is bound, there isn’t nothing built-in from Pixel Caffeine, so might simply call the standard facebook function fbq directly, here an example:

fbq('track', 'AddToCart', aepc_extend_args({
	content_ids: [product_id],
	content_type: 'product',
	content_name: product.find('[itemprop="name"]').first().text(),
	content_category: button.data('download-categories'),
	value: parseFloat( price ),
	currency: currency
}));

aepc_extend_args is a build-in JS function from Pixel Caffeine that extends the parameters adding some other standard parameters for advanced matching.

I hope this can help you to integrate your plugins with Pixel Caffeine, let me know if you need further help. You can reach me on slack too (@antoscarface), I’ll reply you as soon as possible! ??

@antoscarface – The fbq() method may work. We have JS event based tracking in both plugins already using a beacon for tracking opens, conversions, closes and a few others. I definitely think the open & conversion events are crucial and would allow retargeting users who saw an optin but did’t convert for instance.

I’m sure there are dozens of other opportunities with our extension line such as AJAX Login, Age Verification etc.

Would you prefer the code go in your plugin similar to EDD? In which case I would be happy to send a blast to our users and let others know. We could do a connector plugin which gives us both an additional landing page on the repo as another option, or I can wrap it into our core plugin which I’m trying to avoid, so leaning toward option #2.

If the events to add are JS based, I think that the better solution is to call fbq function directly (under a function exists check obviously), from your plugins and only for event firing (and not init), in this way your plugins automatically fire the pixel if there is on the website a facebook pixel initialized (from Pixel Caffeine or any other pixel plugin as well).

Is this may be a good solution? Otherwise, maybe I need more details to understand specifically your needs.