Hyros OG Story Attribution: The Setup That Actually Works

If you're running Facebook story ads and your attribution numbers feel wrong — they probably are. Story placements have a fundamental problem that standard pixel-based setups can't solve: users interact with stories inside a full-screen, swipe-driven environment where the browser context is inconsistent, cookies often don't fire, and the click-to-landing-page journey gets interrupted by Meta's native story UI.

The result is chronic under-reporting. Across the accounts I've audited, story placements under-attribute by 30–60% compared to actual purchases confirmed in Shopify or CRM. You scale down a campaign that's actually printing money because the numbers say it's breaking even.

Hyros's OG (Original) story attribution model exists specifically to address this. But "using Hyros" and "using Hyros correctly for stories" are very different things. Most teams install the pixel, add UTMs, and call it done — and then wonder why their Hyros numbers still don't match reality.

Hyros calls it the "OG" model — Original attribution. It's the proprietary logic Hyros uses to connect ad events to downstream conversions across the full customer journey, as opposed to importing or trusting Meta's own attribution window.

Understanding it requires a quick comparison with the other models you might be running:

The OG model works because it doesn't rely solely on browser-side pixel fires. It layers in server-side events, email address matching (when users opt in on your funnel), and Hyros's own click-tag infrastructure — so even when the story placement drops the cookie, the server event captures the conversion and maps it back to the correct campaign.

Stories specifically need this because the swipe-up (now "tap to open link") behavior frequently opens landing pages inside Meta's in-app browser on iOS, where cookie-based attribution is heavily restricted post-iOS 14.5. Without a server-side layer, you're flying blind on roughly half your iOS traffic.

Before touching any configuration, audit your current setup against these five failure patterns. I see at least three of these in every account I audit.

iOS 14.5 changed the game. Apple's App Tracking Transparency (ATT) framework means that roughly 60–70% of iOS users have opted out of cross-app tracking. For story ads — heavily consumed on mobile — this is catastrophic for pixel-only setups.

The fix is Meta Conversions API (CAPI), routed through Hyros so that server-side events feed into the same attribution model as your pixel events. Here's how to configure it.

Step 1: Generate Your Hyros Server-Side Token

In Hyros, go to Settings → Integrations → Facebook. You'll find a field labeled "Server-Side Access Token." Generate or copy this token — it's what Hyros uses to authenticate server events sent to Meta CAPI on your behalf.

Step 2: Configure Meta CAPI in Hyros

Under the same Facebook integration settings, enable Conversions API and paste your Meta System User token (generated from your Meta Business Manager under System Users). Map your conversion events — at minimum: Lead, Purchase, and InitiateCheckout.

Step 3: Verify the Server Event Payload

Use Meta's Events Manager test tool to confirm your server events are arriving. A correctly configured server event payload looks like this:

{
  "data": [
    {
      "event_name": "Purchase",
      "event_time": 1711324800,
      "action_source": "website",
      "event_source_url": "https://yoursite.com/thank-you",
      "user_data": {
        "em": ["<hashed_email>"],
        "ph": ["<hashed_phone>"],
        "fbc": "fb.1.1711324800.AbCdEfGhIjKlMnOp",
        "fbp": "fb.1.1711324000.1234567890",
        "client_ip_address": "203.0.113.42",
        "client_user_agent": "Mozilla/5.0..."
      },
      "custom_data": {
        "currency": "USD",
        "value": 997.00,
        "order_id": "ORD-20260325-001"
      }
    }
  ]
}

Key fields to verify: fbc (click identifier — must match the fbclid from the ad click), fbp (browser pixel identifier), and hashed email if collected. Without fbc, CAPI can't link the server event to the original story click.

Step 4: Verify Event Deduplication

You will now have both a browser pixel event and a server-side event firing for the same conversion. Without deduplication, Hyros and Meta will both double-count. Set the event_id field to a consistent identifier — typically your order ID or a UUID generated at purchase — in both the pixel and the server event. Meta uses this to deduplicate; Hyros does the same on its side.

UTMs are how Hyros knows which campaign, ad set, and creative gets credit. For story ads, your UTM structure needs to be more granular than what most teams use for feed placements — because stories are a distinct placement with distinct performance characteristics.

Required Parameters

The _story suffix on utm_content is not just a naming convention — it lets you filter Hyros reports to story placements only, so you can compare story ROAS against feed ROAS using the same attribution model.

Full UTM Template

utm_source=facebook&utm_medium=paid_social&utm_campaign={{campaign.name}}&utm_term={{adset.name}}&utm_content={{ad.id}}_story

Bulk Apply in Meta Ads Manager

1. In Ads Manager, select all story ad creatives across your campaigns
2. Click Edit → scroll to Tracking → URL Parameters
3. Paste the template above — Meta will auto-populate the dynamic fields
4. Click Publish — this applies to existing ads without creating new ad IDs
5. Verify by clicking through a story ad preview and checking that the landing page URL contains all five UTM parameters

Single-touch attribution — last-click or first-click — lies to you about stories. A story ad almost never closes a sale on its own. It creates awareness, builds familiarity, and starts a journey that might convert days later via email retargeting, a Google search, or a direct visit. If you credit only the last touch, stories look worthless. If you credit only the first touch, stories look like they're driving everything.

Multi-touch attribution in Hyros solves this by distributing credit across the full journey. Here's how to configure it for story campaigns.

Setting Up Multi-Touch in Hyros

1. Go to Reports → Attribution Settings
2. Set Attribution Model to Multi-Touch (Position Based)
3. Configure position weights: First Touch 40%, Middle Touches 20% (distributed equally), Last Touch 40%
4. Set Click-Through Window to 7 days for story campaigns
5. Set View-Through Window to 0 days until you've validated baseline — then test at 1 day
6. Enable Cross-Device Attribution — critical for mobile story → desktop conversion paths

Attribution Window Logic for Stories

A 7-day click window is appropriate for story ads because the purchase intent triggered by a story often doesn't convert same-session. The user sees the story on Monday, does some research, gets retargeted by email on Wednesday, and purchases on Thursday. The 7-day window captures that full arc. A 1-day window — common in last-click setups — misses it entirely.

The email retargeting ROAS dropped from 11.2x to 4.1x — not because email got worse, but because it was previously taking credit for conversions that story ads initiated. Multi-touch reveals the actual contribution of each channel, which makes budget allocation decisions dramatically more accurate.

A working Hyros story attribution setup should show event-level data in the Hyros event log within minutes of a conversion. Here's how to verify it and what to do when something's off.

Hyros Event Log Check

1. In Hyros, go to Tracking → Event Log
2. Filter by event type: Purchase
3. Find a recent conversion and expand it — you should see the full attribution path
4. Confirm the path includes at least one story ad touchpoint with utm_content ending in _story
5. Check the event source: you should see both Pixel and Server listed — if only Pixel appears, your CAPI setup isn't firing

Cross-Check with Meta Attribution Tool

In Meta Events Manager, run the Attribution Comparison report. Compare Hyros-attributed story conversions against Meta's own count for the same period. You should expect Hyros to report 10–25% more conversions than Meta's last-click default — because Hyros is capturing assisted conversions that Meta misses. If Hyros is reporting fewer than Meta, something is broken in your pixel or CAPI setup.

n8n Workflow for Daily Attribution Gap Check

Manual verification doesn't scale. I run a daily n8n workflow that pulls yesterday's Hyros story attribution data via API and compares it against Shopify orders, flagging any day where the gap exceeds 20%.

This workflow catches problems before they compound. An attribution gap that goes unnoticed for a week means a week of bad scaling decisions — you're either cutting spend on campaigns that are actually working or doubling down on ones that aren't.

Getting Hyros OG story attribution right isn't a vanity exercise. It directly changes downstream decisions: which campaigns you scale, which creatives you kill, how you split budget between top-of-funnel awareness (stories, Reels, YouTube pre-roll) and bottom-of-funnel closers (email, retargeting, Google branded).

The accounts I've audited that had broken story attribution shared a common pattern: they were under-investing in top-of-funnel because the data said it wasn't working. Their email retargeting was profitable — but it was cannibalizing from a shrinking audience because nothing was filling the top of the funnel. Once attribution was fixed, they could see the flywheel: story ads build the audience that email converts.

The full setup covered here — pixel + CAPI deduplication, correct UTM structure, multi-touch position-based model, daily verification workflow — takes about a day to implement correctly. The ongoing maintenance, once the n8n workflow is running, is essentially zero.

If you're working through a Hyros setup and hitting walls — whether it's CAPI integration, funnel redirect issues swallowing your fbclid, or a multi-touch model that just doesn't look right — feel free to reach out. This is the kind of setup work I do regularly for performance marketing teams and agencies.