Tag Manager Integrations
Install Ours Privacy through Adobe Experience Platform Tags, Piwik Tag Manager, Google Tag Manager, or the Ours Privacy Tag Manager.
Tag Manager Integrations
Ours Privacy works with all major tag managers. Choose the one that fits your setup.
| Tag Manager | Integration Type |
|---|---|
| Ours Privacy Tag Manager | Native (recommended) |
| Google Tag Manager | GTM Template |
| Adobe Experience Platform Tags | Extension |
| Piwik Tag Manager | Custom HTML |
We strongly recommend using the Ours Privacy Tag Manager
The Ours Privacy Tag Manager is purpose-built for HIPAA-compliant analytics, and offers tighter integration with the Ours platform. Get started with Ours Privacy Tag Manager →
Adobe Experience Platform Tags
Integrate Ours Privacy into your website using Adobe Experience Platform Tags (formerly Adobe Launch). The Ours Privacy extension lets you track events and identify users without writing code.
Prerequisites
- An Ours Privacy account with a project token
- Access to an Adobe Experience Platform Tags property
Step 1: Install the Extension
- Log in to Adobe Experience Platform Data Collection
- Open your Tags property
- Navigate to Extensions > Catalog
- Search for "Ours Privacy" and click Install
- Enter your Project Token
- Find this in your Ours Privacy dashboard under Settings > Project Token
- Click Save
Step 2: Create the Initialize Rule
The Initialize action loads the Ours Privacy SDK on every page. It must fire before any Track or Identify actions.
- Go to Rules and click Add Rule
- Name it "Ours Privacy - Initialize"
- Under Events, click Add:
- Extension: Core
- Event Type: Library Loaded (Page Top)
- Click Keep Changes
- Under Actions, click Add:
- Extension: Ours Privacy
- Action Type: Initialize
- Click Keep Changes
- Click Save
Step 3: Track Events
Create rules for each event you want to track.
Example: Track Page Views
- Go to Rules and click Add Rule
- Name it "Ours Privacy - Page View"
- Under Events, click Add:
- Extension: Core
- Event Type: DOM Ready
- Click Keep Changes
- Under Actions, click Add:
- Extension: Ours Privacy
- Action Type: Track Event
- Event Name:
page_view - Add Event Properties (optional):
- Key:
page_url/ Value:%Page URL% - Key:
page_title/ Value:%Page Title%
- Key:
- Click Keep Changes
- Click Save
Example: Track Button Clicks
- Create a new rule named "Ours Privacy - CTA Click"
- Under Events, add:
- Extension: Core
- Event Type: Click
- CSS Selector:
.cta-button
- Under Actions, add:
- Extension: Ours Privacy
- Action Type: Track Event
- Event Name:
cta_click - Event Properties:
- Key:
button_text/ Value:%Clicked Element Text%
- Key:
Step 4: Identify Users
Create a rule that fires when a user's identity is known (e.g., after login or form submission).
- Go to Rules and click Add Rule
- Name it "Ours Privacy - Identify User"
- Under Events, add the appropriate trigger (e.g., Custom Event for a login callback, or a Direct Call rule)
- Under Actions, click Add:
- Extension: Ours Privacy
- Action Type: Identify User
- User Properties:
- Key:
email/ Value:%User Email% - Key:
name/ Value:%User Name% - Key:
plan/ Value:%Subscription Plan%
- Key:
- Click Keep Changes
- Click Save
Replace
%User Email%,%User Name%, etc. with your actual data element names.
Step 5: Publish
- Go to Publishing Flow
- Click Add New Library (or edit your working library)
- Add all changed resources
- Build to your Development environment first to test
- Once verified, promote to Staging and then Production
Using Data Elements
Adobe Tags data elements let you dynamically populate values in Ours Privacy actions. Use the %dataElementName% syntax in any text field.
Common data elements to create:
| Data Element | Type | Description |
|---|---|---|
| Page URL | Core - Page Info | Current page URL |
| Page Title | Core - Page Info | Current page title |
| User Email | JavaScript Variable / Custom Code | User's email from your app |
| User Name | JavaScript Variable / Custom Code | User's display name |
Call Ordering
The Ours Privacy extension handles call ordering automatically:
- If Track or Identify actions fire before the SDK has finished loading, the calls are queued
- Once the SDK initializes, all queued calls are sent automatically
- You should still ensure the Initialize rule fires on every page
Troubleshooting
Events not appearing in Ours Privacy
- Verify your project token is correct in the extension configuration
- Check the browser console for error messages starting with "Ours Privacy:"
- Enable Adobe Tags debug mode by adding
_satellite.setDebug(true)in the browser console - Verify the Initialize rule is firing before Track/Identify rules
SDK not loading
- Check that the Initialize action is configured and its rule is active
- Verify no Content Security Policy (CSP) is blocking
https://cdn.oursprivacy.com - Check the Network tab in browser DevTools for failed requests to
cdn.oursprivacy.com
Data elements not resolving
- Ensure your data elements are created and returning values
- Test data elements individually using
_satellite.getVar('dataElementName')in the browser console - Check that data element names match exactly (case-sensitive)
Piwik Tag Manager
Ours Privacy works with Piwik PRO Tag Manager using Custom HTML tags. Add the Ours Privacy Web SDK snippet as a Custom HTML tag triggered on All Page Views, then create additional Custom HTML tags to call ours('track', ...) and ours('identify', ...) as needed.
For full SDK usage details, see the Web SDK documentation.
How is this guide?