Event Tags enable marketers to track key user actions taken by users throughout the customer journey. These events can then be used both for targeting and for insights. Individual events will populate in the Planner section of the platform and can also be used for campaign execution.
There are two ways to track events once the Q Pixel is installed on your website: Rule Based Events and Data Pass-back Events.
Rule Based Events
Rule based events enable you to fire events automatically based on URLs visited or user interactions with specific DOM elements. See our more detailed guide on rule events.
When creating rule events, you may combine multiple conditions to define when the event is fired. All conditions must be true for the event to be fired.
⚠️ You must install the Q Pixel Base Tag to utilize Rule Events.
Data Pass-back Events
Data pass-back events enable you to create page or event specific code snippets.
Place code snippets for custom events on the pages or in event handlers as required by your use case. The code snippet should only be triggered on the event for which it has been created for.
For example, If an event has been created for the Sign In Button, the snippet should only be fired on this website activity.
window._qevents = window._qevents || ;
qacct:"p-123456789", // your pcode
labels:"_fp.event.Sign In Button",
Note: This is a sample only, do not implement this code on your website.
There are two different data pass-back event types.
- Full Tag - This is recommended if the tag is being fired through a tag manager. The full tag can execute on its own without requiring the base tag to be installed on the same page.
- Partial Tag - This is recommended if the tag is being fired on the site directly and on a page where the base tag has already been installed. For the partial tag to fire, the base tag is required to be installed on the same page.