First-party measurement and identity

What Novia measures today

Novia adds naira_click_id to an ad destination after a tracked click. Your server retains that identifier and sends a conversion with a unique event ID and the campaign’s private key. The key belongs on your server, never in public webpage code.

Attribution follows the campaign’s configured 1-, 7- or 30-day click window. Deduplication prevents a repeated event ID from creating a second attributed outcome. Attribution is an accounting rule, not proof that the ad caused the purchase.

What a network identifier does not tell you

The daily frequency guard uses a network-address identifier that resets at midnight UTC. People sharing a connection may share that allowance. It is not a persistent person ID or cross-device identity graph.

Novia does not currently offer automatic cross-device identity resolution or third-party audience profiles. Do not infer that two devices belong to the same customer from a headline, location or shared network.

A considered first-party approach

If your business later links advertising outcomes to signed-in customer records, define the purpose, consent, access and retention before collecting identifiers. Minimize fields and keep customer records outside general AI prompts. A pseudonymous identifier can still relate to a person.

Check your integration

• Retain the click identifier with the relevant order or enquiry.
• Use unique event IDs and the configured conversion action.
• Send values in the documented NGN input unit.
• Keep integration keys secret and server-side.
• Run the receiver test, then separately verify a permitted real attribution path.