An enquiry may follow several interactions: an advert, a website visit, an email and a conversation with your team. Marketing attribution helps you understand which recorded interactions contributed to a defined outcome, so you can make better decisions about budget and follow-up.
For a Nigerian business or organisation, the most useful starting point is often a concrete result: a qualified lead, a booked appointment or a completed signup. This guide shows how to define that result, record useful evidence and build a repeatable reporting process with Yournotify.
Table of Contents
Start with the question you need to answer
“Which channel is best?” is too broad to guide implementation. A better question is: “Which campaigns generated qualified inspection enquiries in Lagos this month?”
That question defines the outcome, audience and reporting period. It also prevents the team from comparing clicks on one channel with qualified leads on another.
| Measurement | What it tells you | What it does not prove |
|---|---|---|
| Delivery | A message reached a reported delivery stage | The person read it or acted |
| Click | A recorded link interaction occurred | A useful enquiry was completed |
| Lead submitted | An enquiry was received | The lead meets your qualification criteria |
| Lead qualified | The enquiry passed your agreed review | A sale was completed |
| Appointment booked | A booking was confirmed | The person attended |
Choose one primary outcome, then use supporting metrics to explain the journey.
Use a real customer journey to choose the right conversion
Consider the test-drive booking journey visible on Toyota by CFAO’s Nigerian website. A visitor can express interest in a vehicle and request an appointment. For an automotive marketer, those actions create useful stages to measure: enquiry, qualification and confirmed appointment.
An automotive business applying this approach with Yournotify could record a submitted request as lead_submitted, a sales-reviewed enquiry as lead_qualified and the confirmed booking as appointment_booked. Those are different outcomes, even when they relate to the same person and vehicle.
Do not report a requested appointment as confirmed simply because the visitor reached a thank-you page. Let the booking process provide the confirmed outcome and preserve the original enquiry reference through the journey.
Industry examples: what should count as success?
| Market or industry | Useful primary outcome | A supporting measure |
|---|---|---|
| Automotive | Confirmed test-drive appointment | Qualified enquiries by model or branch |
| Property | Confirmed inspection booking | Enquiries that meet the agreed location and property criteria |
| Education | Completed signup or qualified admissions enquiry | Applications progressing to the next stage |
| B2B services | Qualified project enquiry | Consultation appointments booked |
| Consumer applications | Completed signup | Subsequent activation tracked in the application |
For a Nigerian business serving several locations, keep the location in your operational reporting. A Lagos campaign and an Abuja campaign may lead to different branches, teams and appointment capacity. Compare outcomes that each team can confirm, using the same reporting window and definition.
Worked example: connect online interest to a booked visit
A visitor follows a campaign link, submits an inspection enquiry and later confirms a visit with your team. Record the observed interaction and the submitted lead first. When the team confirms the appointment, record that later outcome with the matching identity and reference.
Your report can then answer a useful question: Which campaigns contributed to confirmed inspections? Your operational records can explain what happened afterwards, including attendance and sales. Keep those later results available for business analysis without relabelling a lead API event as revenue.
Start with one branch and one outcome, reconcile a sample against the team’s records, then expand once the data agrees.
Step 1: define your outcome and its source of truth
Yournotify’s attribution API supports lead_submitted, lead_qualified, appointment_booked, signup_completed and app_installed. Use the outcome that matches the event you can confirm.
For a property enquiry, the website can confirm submission, while the CRM or responsible team confirms qualification. Write down the rule for a qualified lead before reporting it: for example, a valid enquiry for a property and location your team serves.
Choose one authoritative system for each outcome. If native Forms or imported leads already provide the outcome through a sync, avoid submitting a second copy through a separate integration. More event sources should not mean more credit for the same lead.
Step 2: make campaign naming consistent
Use a small UTM convention across your links. For example:
utm_source=newsletter
utm_medium=email
utm_campaign=lekki_inspections
Keep spelling and case consistent. Email, email and e-mail should not become three accidental reporting groups. Store the original source metadata with the interaction rather than rewriting it when the contact progresses.
Use a stable customer ID to connect relevant interactions and outcomes. Do not use raw email addresses or telephone numbers as public tracking identifiers. Record the actual measurement preference and its reference as part of the implementation.
Step 3: record the interaction through your server
The following JSON is the body for POST https://api.yournotify.com/attribution/touchpoints. Send it with Authorization: Bearer <YOUR_API_KEY> and Content-Type: application/json from your backend.
It illustrates an ad-click interaction. Replace the example IDs, timestamp and campaign values with the real event values. The consent fields must reflect a genuine recorded preference, not a default inserted for every visitor.
{
"attribs": {
"version": 1,
"event_id": "website:visit-123",
"source": "customer_website",
"source_account_id": "example.com",
"kind": "touchpoint",
"occurred_at": "2026-11-15T09:00:00+01:00",
"attribs": {
"subject_id": "customer-123",
"interaction": "ad_click",
"channel": "paid_search",
"utm_source": "google",
"utm_medium": "cpc",
"utm_campaign": "lekki_inspections",
"measurement_consent": "granted",
"consent_reference": "consent-456"
}
}
}
The outer attribs contains the versioned event. The inner attribs contains interaction details. Preserve both levels when adapting the example. The current attribution documentation explains identity matching and supported fields.
Step 4: record the confirmed outcome
When the enquiry is successfully saved, submit the outcome to POST https://api.yournotify.com/attribution/goals using the same server-side authentication.
{
"attribs": {
"version": 1,
"event_id": "website:lead-123:submitted",
"source": "customer_website",
"source_account_id": "example.com",
"kind": "conversion",
"occurred_at": "2026-11-15T09:05:00+01:00",
"attribs": {
"subject_id": "customer-123",
"goal": "lead_submitted",
"conversion_id": "lead-123",
"measurement_consent": "granted",
"consent_reference": "consent-456"
}
}
}
Use the same subject_id for the person’s interaction and outcome. Keep the original event_id and identical payload when retrying an uncertain request. A changed payload under the same event reference can produce a conflict response.
The source, account, goal and conversion ID identify one outcome. A later qualification stage can use the same conversion ID with the different supported goal. Keep revenue calculations in your financial reporting; do not add revenue fields to this lead-outcome payload.
Step 5: generate and compare a report
In Attribution, choose the goal, available attribution model, dates and timezone, then generate the report. Use Africa/Lagos for a Nigerian operating-day view where appropriate.
Keep the model and reporting window consistent when comparing campaigns. Changing both the campaign and the measurement rules makes a result difficult to interpret. Review unattributed outcomes too: missing identity links, missing interaction data or measurement preferences may explain them.
For native Forms and already imported leads, use the available Sync leads workflow where relevant. Source metadata from a form is useful context, but it should not be presented as an observed ad click unless that interaction was actually recorded.
Turn the report into a decision
Suppose two campaigns each cost ₦100,000. Campaign A produces 100 enquiries and 20 qualified leads. Campaign B produces 60 enquiries and 30 qualified leads.
| Campaign | Cost per enquiry | Cost per qualified lead |
|---|---|---|
| A | ₦1,000 | ₦5,000 |
| B | About ₦1,667 | About ₦3,333 |
These are illustrative figures. Campaign A looks stronger if you only count enquiries; Campaign B looks stronger against the qualification goal. Use the result to investigate audience, offer and follow-up quality before changing the budget.
Give the next test a clear hypothesis: “Use the more specific property offer to improve qualification rate.” Keep the reporting rules unchanged so you can assess the result fairly.
Frequently asked questions
Why are some outcomes unattributed? Check identity consistency, event timing, available interaction data and measurement preferences. Do not assign a channel simply to remove an unattributed category.
Is link tracking the same as attribution? Link tracking records interactions. Attribution connects eligible interactions with defined outcomes under the selected reporting rules.
Can I track later lead stages? Yes. Use supported goals such as qualified lead or appointment booked when those events are confirmed, keeping stable references through the journey.
Build a measurement process you can use
Start with one outcome and one campaign. Test the interaction, outcome and report together, then compare the report with your operational records. Open Yournotify and use the attribution API documentation to connect your next campaign to a measurable result.