Frequently asked questions
Short answers, with links into the docs for detail. Cannot find your question? Use the search box at the top of the page.
General
Section titled “General”What is Signals?
Signals is Datahash’s server-side data activation product. It ingests customer data from your sources (website, store, CRM, database, warehouse, files) and delivers conversions and audiences to advertising and analytics platforms through their server-side APIs. Start with the introduction.
Do I need to remove my existing pixels?
It depends where the events come from. Server-side events from a CRM, file, database or warehouse source run alongside your pixels and are deduplicated using shared event IDs, so platforms count each conversion once. See Deduplication.
A Datahash website tag is different. NeoTag and dhPixel replace the platform’s own base code rather than sitting beside it, so pause or remove the platform script for any pixel the tag now handles. Two scripts reporting against the same pixel produce conflicting and duplicated tracking that no shared event ID resolves. See Website tag setup.
Do I need engineers to use Signals?
Most sources and destinations connect through the UI with OAuth or API credentials. Engineering help is useful for the website tag, database credentials, and the Datahash API, but day-to-day mapping and monitoring do not require code.
How fast is delivery?
Website, app and messaging sources send as events happen. CRM, database, warehouse, file and lead generation sources are pulled frequently by Signals, so changes reach your destinations without you triggering anything. See Connecting sources & destinations.
Sources
Section titled “Sources”Which systems can Signals ingest data from?
Websites, apps, 23 CRMs, 12 databases, e-commerce platforms, file and object storage, lead form platforms, warehouses, and a direct API. Browse the source catalog.
My source is not in the catalog. What are my options?
Use the Datahash API to send events from any backend, or land exports in a supported file source such as S3 or Dropbox. You can also request a new integration from the team.
Does connecting a database give Datahash write access?
No. Database and warehouse sources need read access only, scoped to the tables you select. Each source page documents the exact permissions required.
Destinations
Section titled “Destinations”Which ad platforms does Signals deliver to?
Meta, Google, TikTok, LinkedIn, Snapchat, Pinterest, Reddit, X, and OpenAI endpoints across web, offline, lead, audience, and app conversion categories. Browse the destination catalog.
Which sources can feed which destinations?
Compatibility is defined per use case. Every source, destination, and use case page renders the compatibility matrix for it, derived from one shared rule set. Start from the use cases.
How do I test a destination before going live?
Most platforms provide test tooling, such as Meta test event codes and TikTok test events. Each destination page documents its test flow, and the Quickstart covers verification end to end.
Match quality & data
Section titled “Match quality & data”What is EMQ and why does it matter?
Event Match Quality is Meta’s 0 to 10 score for how well your events match to Meta accounts, recalculated from the last 48 hours of data. Meta does not publish a target, so compare a score against its own history. It covers web events only, and EMQ reporting in Signals is scoped to web conversions through the Meta Conversions API Gateway. See Match quality & EMQ and Raise your EMQ score.
How do I improve my match rates?
Map more identifiers (email, phone, name, click IDs), make sure they are captured consistently at the source, and let Signals handle normalization and hashing. See Identifier normalization & hashing.
Will server-side events double count against my pixel?
Not when both carry the same event ID and the same event name. You set the event ID on both copies; Datahash does not generate one for you. See Deduplication.
Security & compliance
Section titled “Security & compliance”Is raw PII sent to ad platforms?
Identifiers that platforms expect hashed are normalized and hashed with SHA-256 before delivery. See PII protection.
How does Signals handle consent?
App sources carry the consent flags the user set, and the Google and TikTok connectors carry that platform’s own consent parameters. What each destination requires is documented on its connector page.
Does Datahash support GDPR and India's DPDP Act?
Yes. Signals acts as a processor on your behalf: you decide what data is sent and on what lawful basis, and Signals processes it under your instructions. Identifiers are hashed before delivery and raw personal data is never persisted, which is what keeps the processing footprint small. For a data processing agreement, or documentation for a security review, contact your Datahash representative.
Billing
Section titled “Billing”How is Signals priced?
Billing is per signal, where a signal is one event going from one source to one destination. The same purchase sent to Meta, Google and TikTok is three signals. For batch sources such as a CRM, cloud storage or FTP, every line uploaded counts as one signal. A plan is chosen when a project is created, and billing sits at the account level.
How do I change my plan or get an invoice?
Plans and invoices sit at the account level rather than per project, so a change applies across every project underneath it. Contact your Datahash representative to change a plan or retrieve an invoice. See Accounts, projects & roles for how the two levels relate.