Website
Overview
Section titled “Overview”Website is the most common event source in Signals. It captures what visitors do on your site, together with the identifiers they provide, and delivers those events to the advertising platforms you run.
Events are collected from your own domain rather than through each platform’s own pixel. A checkout confirmation fired from your own domain is not a third-party request, so it is not subject to the blocking and discarding that browsers increasingly apply to platform pixels. One tag serves every destination, so adding a platform later is a change inside Signals rather than another script on the page.
Setup is in two parts. In Studio you choose which data fields to send and collect the tag code. The installation itself happens in your tag manager. Once the tag is live, Datahash verifies the setup and notifies you by email or in Studio when data starts flowing.
Supported destinations
Section titled “Supported destinations”Destinations supported by Website
Prerequisites
Section titled “Prerequisites”- Access to the DNS settings for your website domain, so the subdomain that makes tracking first party can be set up. Any DNS provider works.
- Access to Google Tag Manager for the site, or to the site code.
- Agreement on which events matter, since a tag is configured per event.
The subdomain is set up once per project, from the Datahash engine icon in Studio, by providing the domain and subdomain name and then adding the DNS records at your provider. If the project already has a subdomain you can skip this. A project holds one subdomain only, so a second subdomain means a second project.
Authentication
Section titled “Authentication”In Studio, open Sources, find the Website and E-commerce category, and click the Website tile. There is no credential to enter and nothing to sign into. The connection is established by the tag you install, which carries the identifier Studio issues for your project.
Configuration
Section titled “Configuration”Subdomain
Section titled “Subdomain”Events are collected through a subdomain of your own site rather than a Datahash address. That is what makes the collection first party: cookies set from your own subdomain survive browser restrictions, and ad blockers treat the request as internal rather than external. Nothing is delivered until it is in place, so this comes before the tag work.
A project holds one subdomain. If the project already has one, skip to Data fields.
- Open the subdomain setup from the Datahash engine icon in Studio.
- Enter the subdomain you want, for example
s2sortracking, and the domain of the site you are tracking. Studio pre-fills the domain from your work email, so check it is the right one. - Studio generates the DNS records. Add them at whichever provider manages your domain. Depending on what you are given, that is either four NS records or a single CNAME.
- The subdomain has to sit under the main domain’s registry, and cannot be hosted as a primary domain in its own right.
DNS changes take time to take effect, so a step that fails immediately after you add the records is usually worth retrying before investigating. See Subdomain setup for the record types and the steps at each provider.
Data fields
Section titled “Data fields”Studio asks which data fields you want to collect before you install anything, on the Configure Data Filter screen. The selectable fields are Click Id, Email, First Name, Last Name and Mobile. Fields that destinations require are pre-selected and cannot be unselected.
Alongside these, a set of default data fields is always sent and is not selectable: Browser Agent, City, Country, IP and Pixel Id.
Select as many fields as you can. Match quality at the destination depends on how many identifiers arrive with the event, so a narrow selection here limits every destination downstream. Click Next.
Tag implementation
Section titled “Tag implementation”Two tags are available and they are mutually exclusive. NeoTag is the general-purpose choice, used where you send events to more than one destination. dhPixel is for a single destination, and replaces that platform’s own base code rather than sitting alongside it. You can move to NeoTag later if you add destinations.
For NeoTag, Migrate Now runs a guided migration of your existing tags across to NeoTag. If you would rather do it yourself, Or Setup Manually gives you the NeoTag code to copy, and the expand icon shows the full code. The dhPixel codes sit under More Setup Options, and are available for Google Ads, Meta, OpenAI, Snapchat and TikTok.
See Website tag setup for the full reference on both tags, including the event list and the data layer mapping.
Installing NeoTag
Section titled “Installing NeoTag”In Google Tag Manager, open Tags and click New, choose Custom HTML as the tag type, paste the NeoTag base code you copied from Studio, name the tag and save it. Then create a second Custom HTML tag for event tracking, holding the event code and a trigger for the event you want to capture, and save that too. Repeat for each event. Submit and publish the container, then click Finish in Studio.
Installing dhPixel
Section titled “Installing dhPixel”In Google Tag Manager, open Tags and find the tag holding the platform’s own base code, searching for the platform name to locate it. Replace that base code with the dhPixel code for the same platform from Studio, then save. Because dhPixel replaces the base code rather than adding to it, note where the original came from before you replace it, since removing dhPixel later means putting the original back.
Then click Preview to validate the tag, connect Tag Assistant by entering your website URL, and click Share to generate a debug link. Send that link to analytics@datahash.com so the implementation can be verified, then click Finish in Studio.
Manage instance
Section titled “Manage instance”Website runs as a single instance, so there is no second one to add. What you can change after setup is the data field selection. Open the source, and on the Overview tab under Website Tag Setup click Edit beside Data Collection, select or deselect fields and confirm.
Data & identifiers
Section titled “Data & identifiers”Personal identifiers are normalized and SHA-256 hashed before they are sent to any destination.
Consent state is read at the moment the event fires and applied per destination, so a visitor who has not consented to marketing is not forwarded to a platform that requires that consent.
Best practices
Section titled “Best practices”- Choose NeoTag unless you are certain you will only ever send to one destination. Moving from dhPixel to NeoTag later means reworking the tags.
- Use the tag manager preview and Tag Assistant before publishing. A tag that fires on the wrong trigger is invisible in reporting and expensive to unwind.
- Where the platform’s own script is still running for the same pixel, pause or remove it once the Datahash tag is live. Two scripts on one pixel produce duplicate tracking.
Troubleshooting & FAQ
Section titled “Troubleshooting & FAQ”The tag does not fire. Check the trigger rather than the tag. An event tag with no matching trigger is silent.
Events fire but nothing reaches the destination. Confirm a destination is connected in the same project, and that the data fields selected in Studio include what the destination needs.
Events are being counted twice. The platform’s own script is still running alongside the Datahash tag for the same pixel. Pause or remove it.
Match rates are lower than expected. Usually a narrow data field selection. Open Data Collection and add the identifiers the destination can use.
The subdomain will not verify. The records are wrong or have not taken effect yet. Check they match what Studio showed, then wait before retrying. See Your subdomain is not resolving.