Send page views, checkouts, and purchases to your analytics and advertising platforms. Choose one connection for each tool, add it in the Campaigns OS workspace, and confirm it with a test order.
Many analytics tools automatically recognize a purchase made through a standard online-store checkout. A Next Commerce campaign uses a custom checkout and offer flow, so those store-theme settings may not see the full journey.
Campaigns OS sends the same useful events directly, including the initial purchase and any post-purchase offers. You only need to tell it which tools should receive them.
This setup covers the campaign experience. It makes sure a purchase is still reported when the shopper checks out through the campaign rather than the standard store theme.
You do not need to learn our internal architecture. Pick the description that matches your current setup, then enter the requested account or pixel ID.
Connect the campaign once, then let your existing tags send conversions to the platforms already managed in your container.
Campaigns OS can send events directly to Meta, RudderStack, or a custom web address without adding a separate tag manager.
For supported analytics and ad platforms, the campaign template handles delivery after the campaign is built.
Connect each tool only once. For example, if TikTok is already configured inside Google Tag Manager, do not also enable the direct TikTok connection. Two connections can report the same purchase twice.
The Campaigns OS workspace stores the tracking choices with the campaign map, so the build and the launch checklist use the same settings.
Open the Campaigns OS workspace and select the campaign you are preparing.
Enable the tools the campaign should use. The workspace will show the fields needed for each connection.
Placeholder values show the expected format but cannot connect a live account. Replace every placeholder with the real value before the campaign is built.
The build process carries the selected connections into the campaign. There is no need to edit generated tracking files by hand.
Visit the campaign as a shopper would. Complete checkout, continue through any post-purchase offers, and reach the receipt page. Then check both sides of the connection.
The campaign debug panel shows whether each enabled tool was ready and whether its events were sent successfully. Clear any setup warning before launch.
Confirm that the analytics or advertising platform received the purchase with the expected value, currency, and campaign information.
A duplicate usually means the same tool was connected in two places. Keep the connection your team intends to maintain and remove the other one.
The workspace separates direct connections from tools delivered by the campaign template, but both are configured in the same Tracking area.
Google Tag Manager Connect once, then manage individual platform tags in your container.
Meta, RudderStack, and custom connections for other systems Campaign events are delivered directly without a separate tag manager.
Google Analytics 4, AppLovin, Taboola, Triple Whale, TikTok, Northbeam, Snapchat, and Pinterest Enter the platform ID in the workspace; the campaign template handles delivery.
Tools such as Hyros and RedTrack currently need a custom connection. A developer can use Google Tag Manager, a custom web endpoint, or the vendor's application programming interface.
The public setup above is enough for most campaign operators. The terms below map those choices to the Campaigns OS configuration and runtime.
Tracking is authored under spec.analytics in the Map Builder Launch stage. The compiler carries the selected providers and vendor IDs into the campaign runtime.
dl_purchase represents the checkout purchase. dl_upsell_purchase represents a separate post-purchase offer.