Overview

Problem Definition
You have a business intelligence (BI) vendor whose tracking pixel or script you need to deploy into your Khoros Aurora community. You want to ensure it loads correctly site‑wide, is manageable, and aligns with your tracking/analytics strategy.

Potential Symptoms

• The pixel never fires (no data in your BI vendor).

• The pixel fires but only on some pages or inconsistently.

• You add it via “Developer Tools” but can’t edit it from the analytics UI.

• You use the UI Add Provider method but vendor isn’t listed among built‑in types.

• You cannot decide whether to use your tag management system or embed code directly.

Solution

Choose one of three paths depending on your vendor’s pixel type and your implementation needs

Note that the code snippets in the article serve only as an example to give you an idea of what deploying this would entail. The actual  development of the feature needs to be done by either your own dev team or via a Professional Service team engagement.

Option 1 — Use Third‑Party Analytics with GTM / GA / Meta Pixel

Use this path if your BI vendor’s tag can be deployed via a supported provider or if you already use Google Tag Manager (GTM) or Google Analytics / Meta Pixel.

Steps:

1. In the Khoros Aurora Admin: go to Account menu → Analytics → Third‑party analytics. (Add third-party analytics to your community)

2. Click Add Provider, choose either GTM, Google Analytics or Meta Pixel. 

3. Enter your container ID or tracking ID, and toggle “Active” ON.

4. If you selected GTM, inside your GTM container you can then add your BI vendor’s script/ tag.

5. Result: The vendor looks like a supported provider, manageable via the analytics UI.

When to pick Option 1

• You already use GTM and your vendor supports deployment through it.

• You want to manage tags via GTM (centralised).

• You want the vendor to show up in the Third‑party analytics page with UI visibility.

Option 2 — Add a Configurable Page Script (custom JS pixel)

Use this path if your BI vendor gives you a custom JavaScript snippet (not just an image pixel) and you want it loaded site‑wide and maintainable via code repository.

High‑level steps:

1. In your community’s Git repository (under res/pagescripts) create a folder for your BI script, e.g. res/pagescripts/bi - Configurable Page Scripts
   

2. In that folder, add:

   • bi.script.json (descriptor)

   • Your JS file(s) (e.g. bi.js)

3. In the res/pagescripts/groups.scripts.json file, add your script entry under whichever loading strategy fits (e.g., “afterInteractive”). Example snippet:
   
   

   {
     "afterInteractive": [
       "bi"
     ]
   }

   
   

4. Example bi.script.json:

   {
     "id": "bi",
     "assets": ["bi.js"]
   }

   Example bi.js snippet:
   
   

   (function() {
     var s = document.createElement('script');
     s.async = true;
     s.src = 'https://cdn.examplebi.com/pixel.js';
     document.head.appendChild(s);
   })();

   (Adapt for your vendor’s snippet.)

5. Deploy the code via your normal Git process. After deployment, the script runs site‑wide following the load strategy.

When to pick Option 2

• Vendor requires a JavaScript snippet (not deployable via GTM or built‑in provider).

• You need full control over when/how the script loads.

• You or a developer team have repository access and can commit/deploy changes.

Important Access Note

If your team does not have repository access or developer resources, then you’ll likely need to involve Professional Services to handle this path. 

Option 3 — Image‑only Pixel via Header & Footer Template (no JS)

Use this path only if your BI vendor gives you a simple 1×1 img pixel (a static tag) and no JavaScript is involved.\

• Aurora: Header and Footer configuration
• Aurora: Text/HTML widget configuration

Steps:

1. In the Khoros Aurora Designer: open the Header & Footer page template.

2. Add a Text/HTML widget in the Header or Footer section.

3. In the widget, select More… → Source code, then paste only the <img> tag provided by your vendor. Save.

4. This ensures the pixel is inserted on every page globally.
   (Note: This approach is limited in flexibility compared to JS.)

When to pick Option 3

• Your vendor supplies only an <img> tag (no JS).

• You want a quick, site‑wide implementation with minimal code.

• You don’t require advanced tag‑management features such as event tracking, asynchronous load control, etc.

Summary

Choose the simplest route that meets your vendor’s requirements and your team’s capabilities:

• If deployable via GTM/GA/Meta → go with Option 1.

• If custom JS required and you have repo/developer access → use Option 2.

• If vendor gives only a static image pixel and you want site‑wide coverage with minimal complexity → use Option 3.

FAQ

Q1: What if my BI vendor isn’t listed in the Third‑party analytics UI?
A1: Then you cannot use the built‑in “Add Provider” for that vendor. You’ll have to use either Option 2 (custom JS) or Option 3 (image pixel) depending on what the vendor provides. This is confirmed by the release notes stating only GTM, GA, Meta Pixel are supported in that UI. 

Q2: Can I still edit or disable a vendor added via Developer Tools?
A2: If you deployed via repository (Option 2) or header/footer (Option 3), you cannot manage it via the Third‑party analytics UI. Management (enable/disable, version control) happens through the code repo or template. The built‑in UI is only for supported providers. 

Q3: What if I don't have access to the Git repository of my instance?
A3: You can either request for a paid Professional Services engagement, or Request Access to Khoros Aurora GitHub Repositories for your dev team