dhPixel

dhPixel is the platform-specific way to collect website events. It replaces an advertising platform’s own base code: you keep the tag you already have in your tag manager and swap the code inside it, so collection moves to Datahash without the rest of your setup changing.

Use it when you are connecting one destination. The code is generated per platform, so a dhPixel installation feeds the platform it was generated for and no other. If you are sending to more than one, use NeoTag instead: it is a single script and its events can go to every destination you have connected.

Before you start

• A website source configured in Studio, with the platform you are connecting selected. The code is generated per platform, so a Meta dhPixel and a TikTok dhPixel are different code. dhPixel is available for Google Ads, Meta, OpenAI, Snapchat and TikTok.
• Your subdomain set up and resolving. See Subdomain setup.
• Access to the tag manager container holding the platform’s existing base code.

Choosing your data fields first

Before the code is generated, Studio asks which user data fields to send with your events, on the Configure Data Filter screen. The selectable fields are Click Id, Email, First Name, Last Name and Mobile. Fields a connected destination requires are preselected and cannot be turned off.

Browser Agent, City, Country, IP and Pixel Id are always sent alongside them and are not selectable.

Select every selectable field you can. Each one raises the share of conversions the destination can match to a person, so a narrow selection here caps the destination regardless of how well the tag is installed.

Installing it

1. Copy the dhPixel code for your platform from Studio.

2. In Google Tag Manager, open the Tags section and find the tag holding the platform’s base code. Searching for the platform name will usually find it.

3. Note where the original base code came from before you overwrite it. Removing dhPixel later means putting that code back.

4. Open the tag and replace the platform base code with the dhPixel code. This is a substitution, not an addition, so the original base code should not remain.

5. Save the tag, then submit and publish the container.

Checking it works

1. From the Tags screen, click Preview.

2. Enter your website URL and connect Tag Assistant to the site.

3. Confirm the tag fires on the action you expect.

4. Click Share to generate a debug link, and send it to analytics@datahash.com so the implementation can be verified.

5. Click Finish in Studio.

Datahash also verifies the implementation from our side once data starts arriving, and you get an email or an in-app notification when it does.

What it collects and which events it supports

The same events as NeoTag, and the same behavior. It reports both browser-side and server-side, and the standard event list is identical. See the event reference.

The only difference is reach. A dhPixel installation feeds the one platform its code was generated for, where a single NeoTag script feeds every destination you have connected.

If events do not arrive

The container was saved but not published. A saved container is not live. Submit and publish it.

The platform’s original base code is still present. Two scripts against the same pixel produce conflicting and duplicated tracking. Check the other tags in the container, not only the one you edited.

The subdomain is not resolving. The script loads from it, so nothing is collected until it does. See Your subdomain is not resolving.

The code was generated for a different platform. A Meta dhPixel in a TikTok tag fires cleanly and reports to the wrong place. Confirm the code you pasted matches the platform you are connecting.