PULSE Campaign Pixel — Video Storyboard

VOThis is your quick guide to installing the PULSE campaign pixel. Let's set it up.

On screen: Title: Campaign Pixel Guide

VOStart with the recommended method, Google Tag Manager. First, grab your pixel: in PULSE, open Activate, then Pixels, click Get pixel code, and hit Copy. In Tag Manager, click New Tag, open Tag Configuration, and choose Custom HTML. Paste your pixel and save. For the trigger, pick All Pages for the whole site, or Some Pages for specific URLs. Give the tag a clear name and save.

On screen: PULSE: Get pixel code → Copy · GTM: New Tag → Tag Configuration → Custom HTML → paste → Save · trigger (All/Some) · name → Save

1

2

3

4

5

6

7

8

VOConversions work the same way. Add another tag, open Tag Configuration, choose Custom HTML, and paste your conversion pixel — then save. This time the trigger is Form Submission: fire it on all forms, or pick specific ones. Tracking a thank-you page instead? Use a Page View trigger that fires when the URL matches your thank-you page. Name it and save.

On screen: New Tag → Tag Configuration → Custom HTML → paste → Save · Form Submission (all/some) · or thank-you URL · name → Save

1

2

3

4

5

6

7

VOWhen your tags are in, hit Submit, then Publish — that pushes everything live to the site.

On screen: Submit → version name → Publish

1

2

VOPrefer to drop the pixel straight into your code? In PULSE, choose Get pixel as an image tracker — this one copies the moment you click it. For site visits, paste it into the page's head tag. For conversions, paste it on your thank-you page, or wherever the action happens, like a button click. Then save and publish.

On screen: PULSE image tracker (site visit + conversion) → copies on click → paste in head / thank-you / button event

1

2

VOTo check it's working, open the Pixels dashboard in PULSE. It refreshes daily — you'll see your pixels start logging loads.

On screen: PULSE Pixels dashboard with load numbers

1

VOOn HubSpot, start with the site-wide tracking code under Settings, Website, Pages — it has to be on every page. Then, still under Settings, Website, Pages, open Site Header and Footer HTML: put your remarketing pixel in the header so it fires everywhere, and your conversion pixel in the thank-you page footer.

On screen: Settings → Website → Pages → Tracking code · Site Header / Footer HTML

1

2

VOTo send a form to a thank-you page, go to Forms, Lead Capture, edit the form, open Options, Set Action, choose your thank-you page, and publish. For the thank-you page itself, open it under Pages, then Settings, Advanced, and paste your conversion pixel into the Footer HTML. To QA, use HubSpot's form analytics, test in an incognito window with pixel-helper tools, and check the HubSpot Ads dashboard.

On screen: Form → Options → Set Action → Choose Page · Thank-you page → Settings → Advanced → Footer HTML · QA

VOOn Shopify, go to Online Store, Themes, Edit Code. Paste your remarketing pixel into theme-dot-liquid, in the head, for site-wide tracking. For product pages, open product-information-dot-liquid and push the product details — ID, name, and price — into the data layer, like this. And for add-to-cart, you'll work in main-cart-dot-liquid. Save as you go.

On screen: Online Store → Themes → Edit code · theme.liquid head · product-information.liquid (+ dataLayer) · main-cart.liquid

1

2

3

4

product-information.liquid — pass product details to the dataLayer (guide p29):

<script>
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
  event: "product_view",
  product_id: "{{ product.id }}",
  product_name: "{{ product.title }}",
  product_price: "{{ product.price | money_without_currency }}"
});
</script>

VOFor checkout, don't edit the theme — go to Settings, Customer Events, and add a custom pixel. Drop your conversion pixel in there, save, and publish; this is the supported way on Shopify Plus. You can also subscribe to your own custom events, like an email signup, and push them to the data layer.

On screen: Settings → Customer Events → Add custom pixel → paste → Save · (optional) subscribe to custom events

1

Optional — subscribe to a custom event, e.g. an email signup (guide p32):

analytics.subscribe("special_email_signup", event => {
  window.dataLayer.push({
    event: "emailSignUp",
    emailCampaignId: event.customData.email_campaign_id
  });
});

VOBefore you go live, test on a duplicate theme, use Shopify's theme preview, check the Customer Events activity log, run a test order, and give it twenty-four hours. The guide also links Shopify's Custom Pixels and GTM-as-a-custom-pixel docs if you need more detail.

On screen: Shopify testing checklist & reference docs

VOYou can also run GTM itself through Shopify. You'll need admin access and your GTM container ID. Go to Settings, Customer Events, open the Custom Pixels tab, and add a pixel named “GTM Container.” Clear the placeholder code, paste in the full GTM snippet, swap in your own container ID, then Save and Connect to switch it on.

On screen: Customer Events → Custom Pixels → Add → name → clear → paste GTM code → replace container ID → Save → Connect

1

2

3

4

5

6

VOWhen you replace the variables, the must-change one is your GTM container ID — and you may also need to update the transaction ID, revenue, and currency to match the store. After a test order, confirm those values, plus product IDs if you mapped them, are landing in the data layer.

On screen: Replace variables (Step 6) + validate the dataLayer

VOOptionally, un-comment the product-ID lines to map product IDs. When you test, use a low-cost product and a dedicated discount code, give the team a heads-up before placing test orders, confirm the values come through, and refund the orders afterward.

On screen: Product IDs (optional) + testing best practices

VOA few common issues: no transaction ID usually means a mapping problem. If GTM isn't loading in checkout, use Customer Events. Missing revenue or currency? Check your totals. Duplicate conversions usually mean a pixel's installed twice. And if it fires in GTM but doesn't report, check your triggers, IDs, deduplication, and attribution.

On screen: On-screen troubleshooting list

• No transaction ID → variable mapping
• GTM missing in checkout → use Customer Events
• Revenue / currency missing → check totals
• Duplicate conversions → pixel installed twice / overlapping installs
• Fires in GTM, not reporting → triggers, IDs, dedup, attribution, consent

VOLast step — email greenbergadops at gmail dot com so the team can confirm traffic, and grant them GA4 access. Once that's done, you're ready to launch.

On screen: email greenbergadops@gmail.com + GA4 access