Learn how to configure required open web tracker fields when creating or updating a campaign on the Canvas (new experience). This article focuses on setting up conversion actions for site engagement, lead generation, and purchase activity so campaigns can measure outcomes accurately.
Know how to create mapped pixels.
Trackers are small pieces of code that capture user behavior across websites, apps, and digital channels. Marketers use them to understand how audiences engage with ads and content, then optimize campaigns by refining messaging, enhancing user experience, and driving conversions.
That said, not every advertiser needs trackers. For example, a brand running an awareness campaign may prioritize visibility over individual user insights, focusing instead on metrics like impressions or reach. Similarly, advertisers in regulated industries or regions with strict privacy laws (e.g. GDPR or CCPA) may lack the infrastructure or consent to collect personal data. In these cases, strategies such as contextual targeting (serving ads based on webpage content rather than user behavior) enable compliance while still delivering relevant, effective advertising.
If you're building a campaign from scratch and sequentially following the Canvas quickstart guide, the Open Web Trackers page is easy to find. It's the next wizard stage. If you're working on an existing campaign and want to edit Open Web Trackers settings, follow these steps:
On the Open Web Trackers page, go to the Tracker Type field and select Universal Pixel. Click the Tracker field and select an option. I'll select Soap General. That's the name I used for a tracker I created in a previous step.
Click the New Conversion Action button. Now, add actions to each mapping that we created. I'll start by adding a conversion goal to the All Pages mapping.
Go to the Action Name field and enter any unique name you like. I'll enter All Pages. so that it's easy to recognise at a glance. BTW, did you notice the period after the word pages? Each label on the illumin platform must be unique. Adding an extra character (like a period) lets me use a familiar label and still enter a unique name.
Click the Mapping field and select the matching mapping record. In this example, it's All pages.
Go to the Conversion Type field and select Site Engagement. Here, I'll apply one of the universal pixels I created on the pixel page to a specific conversion.
Fill in the fields (see below) and then click the Add button to save the conversion action.
After you click the Add button, illumin displays the conversion action in the table. Click the pencil icon to edit the action.
To create a Purchase action, select the Purchase conversion type and then follow the steps described above (e.g. add an Action Name and select a Mapping on the drop-down). If you select this option, the page unhides a field. Go to the Conversion Weight field and select Fixed or Dynamic.
Open Web Trackers capture user actions tied to campaigns so outcomes like site engagement, leads, or purchases appear in reporting. They connect mapped pixels to conversion actions. This setup lets marketers evaluate performance beyond impressions and diagnose issues such as conversions not reporting.
Marketers configure Open Web Trackers when campaigns require outcome measurement such as visits, leads, or purchases. Awareness-only campaigns may skip trackers. Regulated environments may also limit tracker use, which can explain symptoms like journey not spending or missing conversion data.
Open Web Trackers appear as a wizard step for new campaigns and as a settings page for existing campaigns. Marketers open a campaign, select the gear icon at the canvas top, and choose Open Web Trackers from the left menu to edit tracker settings.
Site engagement conversions rely on correct labels, values, and attribution windows. Conversion value guides optimization priority. Post click and post view windows define attribution timing. Repeat windows prevent double counting, which helps explain inflated metrics or unexpected reporting gaps.
Fixed purchase values assign one static number to each conversion. Dynamic values rely on a site code snippet that passes revenue data. Dynamic optimization lets the algorithm prioritize higher-value outcomes and often improves performance analysis when purchase data exists.