CONNECTIONS / Website
Every on-site event, routed to your ad platforms.
The Signals tag captures events first-party from your own domain as visitors act on the site. Each event is hashed, checked against consent, and delivered server-side to every platform you advertise on.
- ● website :: signals live
- > event page_view path=/checkout
- > event purchase value=88.00 EUR
- hash sha256(email,phone) consent=filtered
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 77%
The signal Website yields.
Every kind of signal that moves between Website and the platforms, through one hashed, deduplicated route.
- Web conversions
- A checkout confirmation fired from your own domain is not a third-party request a browser can block or discard the way it sometimes does a platform's own pixel.
Pick your platform. Every use case for it, in one place.
Every way Website data moves, grouped by platform and ranked by how many use cases Website supports.
Meta 2 
Google 1 
LinkedIn 1 
OpenAI 1 
Pinterest 1 
Reddit 1 
Snap 1 
TikTok 1 
X 1 From authorization to delivered signal.
-
Install
Add the Signals tag to your site or tag manager, alongside whatever pixels are already running.
-
Configure
Choose which page and conversion events to capture, from page views to checkout completion.
-
Map
Map captured events to each destination's schema in the visual mapper, one tag feeding every platform.
-
Verify
Confirm delivery in the live debugger, per destination, before campaigns rely on it.
Website questions, answered.
Do we need a separate tag for each ad platform?
No. One first-party Signals tag captures the event once and delivers it server-side to every destination you have mapped, each with its own field mapping and delivery status. Adding a new ad platform is a mapping change inside Signals, not another script added to the page.
What happens to an event when a visitor has not given consent?
Consent state is read at the moment the event fires and enforced per destination, so a visitor who has not consented to marketing is not forwarded to platforms that require it. The event can still be logged for analytics where that consent has been given, without ever reaching an ad platform it should not.
Is any personal data stored by Datahash once an event is captured?
Identifiers such as email and phone are SHA-256 hashed at the moment they leave your server, and Datahash Cloud does not store plaintext PII on its own servers. Teams that cannot let data leave their perimeter at all can run the same tag against a self-hosted Core deployment instead.
NEXT STEP
See your Website data working in every ad platform.
Ready to enable a use case, or still mapping what Website data could do? Our team helps you find the right place to start.
