The Attribution Problem Every Agency Has
Your client is spending $30,000/month on Facebook ads. Facebook Ads Manager says ROAS is 4.2x. But their actual revenue is flat. Sound familiar?
The gap between what ad platforms report and what actually ends up in your client's bank account is where attribution tools earn their keep — or don't.
After implementing Hyros for 40+ clients over the past three years (and being an OG Hyros user since 2021), I've seen every setup mistake, every misunderstanding, and every moment where proper attribution saved a campaign that looked dead on paper.
This is the guide I wish I'd had when I started.
Why Hyros Over Triple Whale, Northbeam, or Pixel-Only Tracking
Let me be direct: Hyros is not the cheapest option, but it's the most accurate for high-ticket and info products.
Here's the core difference:
| Tool | Attribution Method | Best For | |------|-------------------|----------| | Pixel only (Facebook native) | Click-based, cookie-dependent | Low-ticket, impulse buys | | Triple Whale | Multi-touch + MTA | DTC e-commerce | | Northbeam | ML-based attribution | Large e-commerce brands | | Hyros | Email/phone-based ID matching | High-ticket, long sales cycles |
Hyros tracks the person, not the click. When someone clicks an ad, then buys 6 days later via direct email, Hyros connects that revenue to the original ad. Pixels lose that sale every time.
For clients selling $2,000+ offers, courses, coaching programs, or any product with a 3+ day consideration window, Hyros is in a different league.
The Three Setups (and Which One You Actually Need)
Hyros offers multiple tracking modes. Most agencies implement the wrong one.
Setup 1: JavaScript Tag Only
What it is: Drop the Hyros JS tag on your pages, same as Google Analytics.
What you get: Basic pageview and click tracking. Better than pure pixels, but misses server-side events.
Use it when: You're testing Hyros before a full implementation, or the client's tech setup doesn't allow server-side.
The problem: iOS 14.5+, ad blockers, and cookie restrictions all degrade this significantly.
Setup 2: Server-Side API + OG Story Attribution
What it is: Your payment processor (Stripe, ThriveCart, etc.) sends purchase events directly to Hyros via API. Hyros matches buyers to their original ad source using email addresses.
What you get: Real revenue data. Purchase events that can't be blocked.
This is what you should implement for every client.
Setup 3: Full Phone Attribution
What it is: Hyros assigns unique phone numbers to ad traffic. When a lead calls, Hyros knows exactly which ad sent them.
Use it when: The client's business relies on inbound phone calls (service businesses, medical, legal).
The OG Story Attribution Setup (Step by Step)
This is Hyros's signature feature and the most misunderstood. Here's exactly how it works and how to set it up properly.
What OG Story does: When a prospect first engages with your content (clicks a Facebook ad, watches a YouTube video, opens an email), Hyros assigns them a "story" — their original traffic source. This story persists even if they buy 90 days later from a different device.
Step 1: Install the Hyros Tag
<!-- Add to <head> on every page -->
<script>
(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://track.hyros.com/v1/lst/[YOUR_TRACKING_CODE].js'+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','[YOUR_ID]');
</script>
Step 2: Connect Your Ad Accounts
In Hyros dashboard:
- Facebook Ads → Connect account → Grant read access
- Google Ads → Connect via Google Ads API
- YouTube → Connect via YouTube Data API
This lets Hyros pull spend data to calculate true ROAS.
Step 3: Set Up Purchase Event Tracking
For Stripe:
// Stripe webhook → your server → Hyros API
app.post('/webhooks/stripe', async (req, res) => {
const event = stripe.webhooks.constructEvent(
req.body, req.headers['stripe-signature'], process.env.STRIPE_SECRET
);
if (event.type === 'payment_intent.succeeded') {
const paymentIntent = event.data.object;
// Send to Hyros
await fetch('https://api.hyros.com/v1/api/v1.0/leads/purchase', {
method: 'POST',
headers: {
'API-Key': process.env.HYROS_API_KEY,
'Content-Type': 'application/json'
},
body: JSON.stringify({
email: paymentIntent.receipt_email,
revenue: paymentIntent.amount / 100,
currency: paymentIntent.currency.toUpperCase(),
event_name: 'purchase'
})
});
}
});
Step 4: Configure OG Story Rules
In Hyros Settings → Attribution:
- Attribution window: 90 days (not 7 or 28 — high-ticket sales take time)
- Story priority: Paid traffic > Organic > Direct
- Multi-touch: Enable "First Touch + Last Touch" credit split
Step 5: Set Up Lead Tracking
If your funnel has a lead capture step (opt-in, book-a-call), track it:
// On opt-in form submission
hyros.trackLead({
email: formData.email,
phone: formData.phone, // optional but improves match rate
event_name: 'lead'
});
The Most Common Hyros Mistakes (and How to Avoid Them)
Mistake 1: Not Mapping Your Funnel
Hyros needs to know your full funnel path to attribute correctly. Most people just install the tag and hope for the best. Instead:
- Map every URL in your funnel (ad → landing page → opt-in → sales page → checkout → thank you)
- Add the Hyros tag to every single page
- Set up events at each stage (lead, add-to-cart, purchase)
Mistake 2: Short Attribution Windows
Setting a 7-day attribution window for a $5,000 coaching program makes no sense. We've seen deals close 45+ days after the first ad click. Set your window to match your actual sales cycle.
Mistake 3: Not Excluding Internal Traffic
Your team clicks through your own ads constantly during testing. Exclude your office IPs or you'll inflate your data.
In Hyros Settings → Filters:
- Add IP exclusions for your office, VPN, and common team locations
Mistake 4: Ignoring the Phone Match Rate
Hyros's accuracy depends on matching purchase emails to ad click emails. If your payment processor doesn't capture email, your match rate tanks.
Check your match rate under Dashboard → Data Quality. Anything below 70% needs investigation.
Mistake 5: Only Looking at ROAS
ROAS is a ratio. If you cut ad spend in half but revenue stays flat, ROAS looks better but you're actually losing. Always look at:
- Revenue attributed (absolute dollars)
- Cost per acquisition (CPA)
- Revenue per lead (RPL)
- Lifetime value of attributed cohorts
Hyros + n8n: The Reporting Stack That Changes Everything
Once you have clean Hyros data, automate the reporting. This is the stack we use at Vixi:
Hyros API → n8n → Claude (narrative generation) → SendGrid (client email)
Weekly trigger in n8n:
- Pull Hyros data for each client via API
- Calculate week-over-week changes
- Identify top-performing and underperforming campaigns
- Claude writes a plain-English summary: "Your Facebook campaign targeting homeowners 35-55 generated $47,200 in tracked revenue this week, up 23% from last week. Your Instagram campaign to lookalike audiences is underperforming with a 0.8x ROAS — recommend pausing and reallocating to the Facebook campaign."
- Email to client Friday at 5pm
Clients love the narrative summaries. They don't have to interpret dashboards — they just know what's working.
Is Hyros Right for Every Client?
Honest answer: no. Hyros pricing starts at $77/month and scales up. For a client spending $2,000/month on ads, the ROI math often doesn't work.
Hyros makes sense when:
- Ad spend is $10,000+/month
- Average order value is $500+
- Sales cycle is longer than 7 days
- You're running multi-channel campaigns
Stick with pixels when:
- Ad spend is under $5,000/month
- You're selling low-ticket products (<$100)
- All sales happen within hours of the ad click
Want Us to Set Up Hyros for Your Business?
We've implemented Hyros for 40+ clients across e-commerce, coaching, SaaS, and service businesses. We handle the full setup: tag installation, API integrations, OG story configuration, and custom reporting dashboards.
Book a free Hyros audit — we'll review your current tracking setup and tell you exactly where you're losing attribution data.