This handbook was originally created as a private operating reference for our clients after completing their Hyros implementation. We decided to publish it here because accurate tracking does not end after setup. Any team using Hyros needs a clear maintenance process to protect attribution quality, avoid silent tracking breaks, and keep leads, calls, purchases, refunds, recurring revenue, and ad-platform events aligned as the business changes.

Your Hyros setup is designed to connect traffic sources, leads, booked calls, direct calls, purchases, refunds, recurring revenue, and ad-platform optimization data. It is not a one-time installation. It is a tracking system that needs to be preserved whenever your funnels, offers, checkout, CRM, ads, domains, email/SMS flows, or integrations change.

Use this handbook as your long-term operating reference after project completion. It is written to work across different Hyros setups, including ecommerce stores, webinar funnels, application funnels, call funnels, info-product funnels, conference funnels, CRM-driven sales processes, and mixed paid/organic acquisition systems.

When you need exact setup steps for a specific platform, use this handbook first to understand what must be maintained, then consult the relevant official Hyros documentation:

How Hyros Stays Accurate

Hyros depends on five things staying aligned:

  1. The visitor is tracked on the right pages.
  2. The visitor’s ad/source identifiers are preserved.
  3. The lead, call, sale, or custom event means the same thing over time.
  4. The revenue source feeding Hyros is complete and not duplicated.
  5. The conversion events sent back to ad platforms match the campaign optimization strategy.

Most Hyros issues come from one of these breaking quietly after a launch, page edit, checkout change, integration refresh, new ad account, or new campaign URL.

Source Of Truth

Every setup needs a clear source of truth for revenue.

Common sources of truth:

  • Shopify, WooCommerce, BigCommerce, Magento, or another ecommerce platform
  • Ontraport, HubSpot, Salesforce, Close, Pipedrive, GoHighLevel, Keap, or another CRM
  • Stripe, PayPal, Authorize.net, NMI, Square, Braintree, Chargebee, Recurly, or another payment platform
  • ClickFunnels, ThriveCart, SamCart, Kajabi, Kartra, Zaxaa, PayKickstart, CheckoutChamp, or another checkout/funnel system

Maintenance rule: avoid sending the same sale to Hyros through multiple paths unless the setup was intentionally built and tested for that. If the CRM or ecommerce platform already receives all payment gateway transactions and feeds Hyros, do not also connect the same payment processors directly to Hyros without confirming deduplication behavior.

Examples:

  • If Ontraport receives PayPal and Stripe transactions, then Ontraport can be the source that feeds Hyros.
  • If Shopify is the ecommerce source of truth, use the Shopify integration as the main sales source and add optional add-ons only where needed.
  • If sales happen through reps after a booked call, make sure the rep uses the same email or identity that Hyros saw during booking, because Hyros uses that identity chain to connect payment back to the original source.

Official reference: How Hyros payment tracking works.

Core Maintenance Principle

Before changing anything, define the business event first.

  • A lead should mean a real lead action, not a generic page view.
  • A call should mean a booked call, completed call, qualified call, or another explicitly defined call event.
  • A purchase should come from the system that reliably records completed transactions.
  • An upsell or order bump should have a clear revenue treatment: same order, separate order, subscription, payment plan, or post-purchase sale.
  • A show-up, no-show, disqualified call, or closed sale should map to the CRM status or booking event that actually proves it happened.

Do not optimize campaigns against events that are easier to fire but less meaningful. A page visit labeled as a lead will eventually damage decision quality.

Change Risk Levels

Low-risk changes still need a quick check:

  • Updating page copy
  • Swapping images
  • Editing an email without changing links
  • Changing ad creative without changing URL parameters
  • Updating product descriptions without changing checkout logic

Medium-risk changes need a same-day tracking check:

  • New landing page
  • New thank-you page
  • New ad URL
  • New email/SMS campaign links
  • New upsell or order bump
  • New funnel step
  • New organic or influencer campaign link
  • New product in the same checkout platform

High-risk changes should be treated as a tracking review:

  • New domain or subdomain
  • New checkout platform
  • New CRM or ecommerce platform
  • New payment processor
  • New Meta pixel, Google conversion action, ad account, or business manager
  • New booking platform or call-tracking flow
  • Major website/theme rebuild
  • New server-side event setup
  • Large campaign launch with a new funnel architecture

New Funnel Checklist

Run this checklist for every new funnel.

  • Identify the funnel type: ecommerce, webinar, opt-in, call booking, application, conference, checkout-only, or hybrid.
  • List every page: landing page, opt-in, VSL, quiz, application, booking page, checkout, upsell, down-sell, order bump, thank-you, confirmation, webinar room, replay page.
  • Confirm Hyros tracking is installed on every page that needs to observe source, lead, call, or purchase behavior.
  • Confirm the opt-in or lead event fires only after the meaningful lead action.
  • Confirm the checkout or purchase event is connected to the chosen source of truth.
  • Confirm all redirects preserve parameters.
  • Confirm the final URL retains fbclid, gclid, fbc_id, gc_id, UTMs, email parameters, influencer parameters, and any Hyros-specific parameters.
  • Confirm the new funnel does not reuse old event names in a misleading way.
  • Confirm the new funnel is included in reporting filters, URL rules, tags, or website segmentation if those are used.
  • Confirm server-side events still go to the correct ad-platform destinations.

Official reference for generic script checks: Opt-in tracking event troubleshooting.

Landing Pages And Redirects

Redirects are a common source of attribution loss.

Watch for:

  • Non-trailing-slash URLs redirecting to trailing-slash URLs
  • HTTP to HTTPS redirects
  • www to non-www redirects, or the reverse
  • Shortlinks such as Bitly
  • Linktree-style intermediate pages
  • Funnel-builder redirects
  • CMS canonicalization
  • Language/country redirects
  • Checkout redirects
  • Payment-processor redirects

Rule: test the exact live URL from the ad, email, SMS, or influencer link. The final resolved URL should still contain the required tracking parameters. Hyros’ Facebook and Google troubleshooting docs both warn that redirects or shorteners can drop parameters and break tracking.

Official references:

New Offers, Products, Upsells, And Order Bumps

Any monetization change can affect revenue attribution.

Before launch:

  • Confirm the product exists in the checkout, CRM, or ecommerce platform that feeds Hyros.
  • Confirm product name, product ID, price, currency, quantity, order ID, and customer email are passed consistently.
  • Confirm order bumps and upsells are either included in the original order or intentionally tracked as separate sales.
  • Confirm failed payments, refunds, partial refunds, subscription renewals, payment plans, trials, and chargebacks behave as expected in the source of truth.
  • Confirm the purchase value sent back to Meta or Google still reflects the desired optimization signal.
  • Confirm new offers are not excluded by product filters, sales rules, blacklists, whitelists, CRM field logic, or automation rules.

After launch:

  • Verify the first few real purchases manually.
  • Compare Hyros against the source of truth by customer, timestamp, amount, product, and order ID.
  • Do not rely only on dashboard totals during the first day. Aggregates can differ because of timezone, attribution window, sync delay, refunds, unpaid orders, filters, or reporting model.

Checkout Changes

Review Hyros whenever you change:

  • Checkout platform
  • Checkout URL
  • Embedded checkout
  • External payment page
  • One-click upsell flow
  • Order bump
  • Subscription app
  • Payment processor
  • Tax/shipping calculation
  • Coupon/discount logic
  • Multi-currency handling
  • Post-purchase flow
  • Thank-you page

Edge cases:

  • If checkout is embedded in an iframe, confirm whether Hyros can observe the user identity and conversion correctly.
  • If payment occurs off-site, confirm how the sale returns to Hyros.
  • If sales reps manually process payments, require a consistent email match between the call booking and payment.
  • If invoices are paid later, confirm whether and when Hyros receives the sale.
  • If a platform records taxes, shipping, tips, or fees as separate line items, confirm whether Hyros should include or exclude them from revenue.

Platform-specific official references:

Ecommerce Maintenance

For Shopify, WooCommerce, and similar stores:

  • Recheck Hyros after theme changes.
  • Recheck Hyros after checkout changes.
  • Confirm add-to-cart tracking if it is part of the setup.
  • Confirm customer email is available to Hyros.
  • Confirm product and order data still reaches Hyros.
  • Confirm subscription apps, cart apps, landing-page builders, post-purchase apps, and PayPal add-ons are included if used.
  • Confirm imported historical sales are interpreted correctly. Historical imports may help LTV calculations but usually do not recreate source attribution from before tracking was active.

Official Shopify reference: Shopify setup guide.

CRM And Sales Pipeline Maintenance

If your Hyros setup depends on a CRM, keep these stable:

  • Contact email field
  • Phone field
  • Lead source field
  • Pipeline stage names
  • Opportunity/deal status
  • Call outcome labels
  • Disqualification reasons
  • Closed-won logic
  • Refund/cancellation logic
  • API keys and integration permissions

Ask for a tracking review when:

  • You rename CRM stages.
  • You add a new pipeline.
  • You change how calls become opportunities.
  • You change the field that stores source, email, or phone.
  • You add manual sales entry.
  • You change the rep workflow for processing payments.
  • You replace or reconnect the CRM integration.

If Hyros tracks show-up calls, qualified calls, or sales calls, status names matter. A simple CRM rename can break reporting if automations or rules are looking for the old value.

Booking And Call Tracking

Hyros can support booked-call tracking, direct call tracking, and call-quality logic depending on the setup.

Booked-call maintenance:

  • Confirm the booking page is tracked.
  • Confirm the booking platform still passes email and phone.
  • Confirm confirmation pages or redirect URLs preserve required parameters.
  • Confirm booked, canceled, rescheduled, no-show, show-up, and qualified statuses are still mapped correctly if used.
  • Confirm the call event in Hyros matches the business definition you use for reporting.

Direct-call maintenance:

  • Confirm number replacement is firing on the site.
  • Confirm calls forward to the correct number.
  • Confirm the minimum call-duration threshold still matches your reporting goal.
  • Confirm call-duration tags still represent the intended call stages if used.
  • Increase the number pool if traffic and call volume grow enough to reduce visitor-level matching accuracy.

Official references:

Domains, Subdomains, And Tracking Scripts

Website changes can break tracking even when the visible site still works.

Review Hyros after:

  • New domain
  • New subdomain
  • Domain migration
  • CMS migration
  • Theme update
  • Header/footer plugin change
  • Google Tag Manager change
  • Consent banner change
  • Cookie/privacy policy change
  • Checkout domain change
  • CDN, caching, or security plugin change
  • DNS or proxy change

Checklist:

  • Hyros script exists in the correct global location.
  • Hyros script is the right one for the domain.
  • The script loads on all funnel pages.
  • The script is not blocked by consent settings beyond your intended policy.
  • The thank-you or confirmation page contains the required tracking.
  • The landing page and post-opt-in page are both tracked.
  • The tracking code is copied from the correct Hyros account.

Official references:

Paid Ad Maintenance

Every new ad or campaign should preserve Hyros parameters.

Meta: fbc_id={{adset.id}}&h_ad_id={{ad.id}}

If UTMs already exist, append Hyros parameters with &, not a second ?.

Example: utm_source=facebook&utm_campaign=spring_sale&fbc_id={{adset.id}}&h_ad_id={{ad.id}}

Google Campaign Types

Performance Max: {lpurl}?gc_id={campaignid}&g_special_campaign=true

Campaigns: ?g_special_campaign=true&gc_id=<campaign_id>

non-PMax campaign types: {lpurl}?gc_id={campaignid}&h_ga_id={adgroupid}&h_ad_id={creative}&h_keyword_id={targetId}&h_keyword={keyword}&h_placement={placement}

Important Google edge cases:

  • Smart Campaigns often require manually finding the campaign ID and appending it to the landing page.
  • Google can prioritize ad-level parameters over ad-group-level parameters. Keep all parameters at the same level if Hyros parameters disappear.
  • Hyros’ Google troubleshooting guidance warns not to connect with a Google MCC/manager account when the direct ad account is required.
  • Hyros’ Google troubleshooting page notes Google experimental campaigns may not be trackable in the documented flow.

Official references:

Ad Accounts, Pixels, Datasets, And Event Routing

If you create or change ad-platform destinations, recheck Hyros.

Review when:

  • New Meta pixel
  • New Meta dataset
  • New ad account
  • New Business Manager or business portfolio
  • New Google Ads customer account
  • New conversion action
  • New TikTok, Snapchat, Pinterest, LinkedIn, Bing, Reddit, X, or other paid-source account
  • Agency or staff access changes
  • OAuth/token refresh is required
  • Events are moved from a custom event to a standard event

Rules:

  • Campaigns should optimize for the event Hyros is actually sending when Hyros is part of the optimization strategy.
  • Do not rename conversion events without updating the Hyros mapping.
  • Do not switch pixels or conversion actions without verifying server-side event delivery.
  • If an agency user who connected the integration is removed, reconnect the integration from an account that will keep access.

Official reference for verifying event delivery: Verifying events sent from Hyros to your ad platform.

UTMs, Hyros Parameters, And Naming Standards

Use UTMs for human-readable reporting across tools. Use Hyros parameters for source matching and attribution. They are complementary.

Maintain:

  • utm_source
  • utm_medium
  • utm_campaign
  • utm_content
  • utm_term
  • Hyros ad IDs and campaign IDs
  • Email identity parameters
  • Influencer/source parameters
  • Organic campaign parameters

Rules:

  • Keep naming stable.
  • Avoid spaces and inconsistent capitalization in manually created values.
  • Do not overwrite Hyros parameters with UTM-only tracking.
  • Do not let shortlinks, redirect tools, or page builders strip parameters.
  • Test final URLs after publishing.
  • If a URL already has ?, append additional parameters with &.

Email And SMS Maintenance

Email and SMS flows need source tracking because they often drive late conversions.

Review when:

  • New broadcast
  • New automation
  • New abandoned cart flow
  • New webinar reminder flow
  • New SMS campaign
  • Email platform migration
  • SMS platform migration
  • New link shortener
  • New link tracking setting
  • New personalization/merge-field syntax

Checklist:

  • Every website/funnel link includes the agreed Hyros/email/SMS parameters.
  • Cloned flows preserve parameters.
  • The email field merge tag resolves correctly.
  • Links do not redirect through a tool that drops parameters.
  • If using a custom email domain, confirm tracking still works.
  • If sales happen after multiple emails, tag each meaningful link, not just the first email.

Klaviyo example: ?he={{ email }}&el=email

Official references:

Organic, Influencer, Partner, And Affiliate Tracking

Organic tracking can be source-level or campaign-level.

Source-level organic tracking answers: “Did this come from Google, YouTube, Instagram, Facebook, Reddit, Pinterest, blog, direct, or another source?”

Campaign-level organic tracking answers: “Which specific influencer, partner, post, newsletter, video, or organic campaign drove this?”

Maintenance rules:

  • Use Previous URL/referrer logic for broad organic source rules when applicable.
  • Use explicit links for campaign-level organic tracking.
  • Keep influencer names or partner IDs normalized.
  • Do not reuse the same campaign parameter for different partners.
  • If an influencer changes bio links or link-in-bio tools, retest parameter preservation.
  • If affiliate software is introduced, decide whether Hyros, the affiliate platform, or both should be the reporting source.

Influencer example: https://example.com?influ={influencer_name}

Forms, Quizzes, Applications, And Lead Capture

Lead capture often breaks when forms are embedded, replaced, or redirected.

Checklist:

  • The page containing the form is tracked.
  • The post-submit page is tracked.
  • The form passes email using a parameter Hyros can recognize if the setup depends on URL parameters.
  • The redirect URL preserves email and source parameters.
  • The lead event represents real form completion, not just page arrival.
  • Quiz tools, application forms, and embedded forms are tested with a real submission.

Official Hyros form guidance emphasizes the importance of email for tracking and notes that some forms need the email passed as email= in the redirect URL. Reference: LeadQuizzes forms.

Reporting Maintenance

Use the Hyros panel and the Hyros Chrome extension for different jobs.

Hyros panel:

  • Inspect recent leads, calls, and sales.
  • Click individual contacts to review journeys and purchases.
  • Filter by tag, source, campaign, action, website, or funnel.
  • Create aggregate reports when the question is about performance by source, campaign, or date.

Hyros Chrome extension:

  • Use it inside ad managers for campaign-level context.
  • Paste the Hyros API key from the correct account.
  • Sync the ad account.
  • Enable Hyros data.
  • Keep campaign/ad ID columns visible where required.
  • Refresh the ad manager after setup changes.
  • Select the attribution model that matches the reporting question.

If the extension looks wrong, compare against the Hyros panel before assuming Hyros data is wrong. Extension issues can come from syncing, hidden ID columns, cached data, duplicate names, wrong attribution model, or a core tracking issue.

Official references:

Revenue Reconciliation

When Hyros revenue does not match the source of truth, work in this order:

  1. Confirm date range and timezone.
  2. Confirm whether refunds, failed payments, unpaid orders, subscriptions, taxes, shipping, discounts, and payment plans are included the same way.
  3. Compare individual transactions, not only totals.
  4. Check whether all payment methods feed the source of truth.
  5. Check whether the source of truth feeds Hyros.
  6. Check whether the same sale is entering Hyros twice through two integrations.
  7. Check whether a new product, upsell, checkout, or payment method bypasses the old path.
  8. Check whether Hyros was fixed after the period being reviewed; historical gaps may need import/backfill.

Practical rule: if aggregate totals disagree, inspect the last 10-20 real transactions one by one.

Event Delivery To Ad Platforms

If Meta, Google, TikTok, Snapchat, or another ad platform does not show expected events:

  • Confirm Hyros captured the lead/call/purchase first.
  • Confirm the Hyros integration to the ad platform is connected.
  • Confirm the correct pixel, dataset, account, or conversion action is selected.
  • Confirm the event is mapped to the event the campaign optimizes for.
  • Confirm match identifiers are available where required.
  • Confirm values and currency are present for purchase events.
  • Confirm failed events are retried or resent if supported.

Official reference: Verifying events sent from Hyros to your ad platform.

Privacy, Consent, And Data Quality

Tracking quality and privacy controls interact. Review both when making changes.

Watch for:

  • Consent banner blocking scripts before consent.
  • Shopify customer privacy/customer event settings.
  • Browser privacy changes.
  • Cookie duration changes.
  • Server-side events missing email, phone, IP, user agent, or click ID.
  • Email normalization issues.
  • Phone number formatting issues.
  • Users entering one email at opt-in and another at checkout.

Hyros may connect user journeys across multiple emails or identifiers in ways that your CRM does not. When identities differ, compare name, timestamp, amount, order ID, and journey before concluding a transaction is missing.

QA After Every Launch

Run this after every meaningful launch or tracking-sensitive change.

  • Open the exact ad/email/SMS/influencer URL.
  • Confirm parameters survive the final redirect.
  • Submit a real or controlled test lead.
  • Complete or observe a real purchase.
  • Confirm the lead appears in Hyros.
  • Confirm the purchase appears in Hyros.
  • Confirm the CRM/ecommerce source and Hyros match by customer, timestamp, amount, product, and order ID.
  • Confirm Meta/Google receives the intended server-side event if active.
  • Confirm values and currency are correct.
  • Confirm source tags or URL rules apply correctly.
  • Confirm direct-call or booked-call records appear if relevant.
  • Re-check after the first few real conversions.
  • Re-check again after 24-48 hours if ad-platform cost/import data or delayed syncs are involved.

Troubleshooting Map

Missing leads:

  • Check script on landing and thank-you pages.
  • Check form redirect.
  • Check email parameter.
  • Check whether the event is a real lead action.
  • Check the correct Hyros account/script.

Missing sales:

  • Check source of truth.
  • Check payment method.
  • Check product/checkout path.
  • Check CRM/ecommerce integration.
  • Check duplicate or missing payment-processor paths.

No attribution:

  • Check ad/source parameters.
  • Check redirects and shortlinks.
  • Check final URL.
  • Check click IDs.
  • Check source rules.

Duplicate sales:

  • Check whether CRM/ecommerce and payment processor both send the same sale.
  • Check whether upsells are intentionally separate.
  • Check subscription renewal handling.

Wrong ad-platform event:

  • Check Hyros event mapping.
  • Check pixel/dataset/conversion action.
  • Check campaign optimization event.
  • Check integration token/access.

Chrome extension mismatch:

  • Check API key.
  • Check account sync.
  • Check ID columns.
  • Check date range and attribution model.
  • Compare to Hyros panel.

When To Request A Hyros Review

Request a review before or immediately after:

  • New funnel
  • New product or offer
  • New checkout platform
  • New payment processor
  • New CRM
  • New booking platform
  • New domain/subdomain
  • New ad account or pixel
  • New conversion action
  • New email/SMS platform
  • Major site rebuild
  • New upsell/downsell/order bump
  • New subscription/payment-plan flow
  • New call tracking setup
  • Unexplained discrepancy between Hyros and the source of truth
  • Sudden drop in tracked leads, calls, purchases, or ad-platform events

Client-Specific Notes Template

Customize this section for each client before sending the handbook.

Primary revenue source:
Payment processors:
Checkout platform:
CRM:
Booking/call platform:
Website/funnel platform:
Primary ad platforms:
Meta pixel/dataset:
Google Ads conversion actions:
Email/SMS platform:
Primary domains/subdomains:
Hyros events sent to ad platforms:
Required URL parameters:
Known redirect/domain rules:
Launch QA owner:
When to request support:

Related blog posts

Leave a Reply

Your email address will not be published. Required fields are marked *