Step-by-step setup protocols, troubleshooting guides, and technical documentation for your Data Bridge attribution engine.
No matches. Try a different term, or submit an operator ticket below.
Work through these in order — each one assumes the previous is complete.
Links incoming WhatsApp chats directly to the original ad campaign and UTM parameters that produced them.
Log into your Data Bridge dashboard and copy your unique WhatsApp link template containing the encrypted session token:
Replace standard wa.me links on your landing pages and website buttons with the Data Bridge dynamic link script.
Click your WhatsApp button from an incognito browser window, then check your Data Bridge live log to confirm the click recorded the session ID, device type, and landing page URL.
If nothing appears in the live log within a few seconds, the button is still using a plain wa.me link — recheck step 2 before troubleshooting anything else.
Connect Meta Conversions API and Google Ads offline conversion import so verified lead signals flow back to the ad platforms.
The conversion action name must match exactly, including capitalisation and spacing — a mismatch is the most common cause of uploads silently failing.
Retroactively match closed deals back to the original ad keyword and ad spend that produced them.
Deal amounts must be sent as a plain number. Currency symbols, ranges, or text in that field will break the revenue match.
The four issues operators raise most often, and what to check first.
Browser tracking pixels routinely lose a substantial share of conversion data to ad blockers, iOS privacy restrictions, and instant bounces — commonly cited in the range of 20–35%, though it varies by audience and device mix.
Data Bridge captures conversions server-side at the moment a link is clicked or a form is submitted, so it sees events the browser pixel never reports. A higher count in Data Bridge is expected, not an error.
Data Bridge is built to avoid the trigger that normally makes a banner necessary: it relies on first-party server telemetry from voluntary user actions — clicking a WhatsApp link, submitting an enquiry form — and does not drop third-party tracking cookies onto a visitor's device.
Consent obligations still depend on everything else running on your site (other pixels, chat widgets, analytics tools) and on how you handle the personal data you collect. We'll walk through your specific setup during onboarding.
Note: this is general product guidance, not legal advice. Confirm your final consent posture with your own data protection officer or legal counsel.
Data Bridge attaches a unique first-party token to the visitor at first contact. When your sales team marks the deal Closed-Won in your CRM weeks later, Data Bridge matches that token and logs the revenue retroactively against the original campaign and keyword.
Nothing needs to be remembered or re-entered by the rep — the token does the joining.
Go to Data Bridge → Live Telemetry and send a test message using your website's WhatsApp button. A new entry should appear within about five seconds showing your device information and campaign source.
If it doesn't, work back through guide 01 — an untagged button is the usual cause.
How your customer data is handled, and who owns it.
Personal identifiers — phone numbers, email addresses — are hashed with SHA-256 before they leave your server environment.
Built in accordance with Malaysian and Singaporean Personal Data Protection Act requirements, with first-party collection as the default.
Customer data remains your first-party property. OVA Intelligence never stores raw personal data or sells conversion insights to third parties.
For custom CRM mapping issues, webhook sync discrepancies, or help configuring a new ad channel, send this straight to our technical integration team.
Response within 1 business day · Mon–Fri, 9:00–18:00 MYT / SGT