Weave → Pinterest · Conversion tracking
Connecting Weave to Pinterest
Weave combines the practice phone system with messaging and scheduling, which makes it one of the few places where the call that actually books the patient is a measurable event. Pinterest is a save-now-buy-later platform, which makes its attribution window the loosest of any network here and its conversion data the most delayed. The join between them succeeds or fails on one thing: whether the epik click identifier reaches the Weave call or booking before the conversion happens, because Pinterest can only match a conversion it can tie back to a click it recognizes.
✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.
Written guarantee
95%+ conversion accuracy on Weave → Pinterest
Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.
Built on — and certified for — the platforms that matter
Stape
Pro Partner
Meta
Tech Provider
Tag Manager
TikTok
Events API
Microsoft
UET Partner
CAPI Partner
CAPI Partner
Built on the same partner stack used by enterprise DTC brands.
By the numbers
No fake testimonials.Just the math.
70+
Platforms supported
Shopify · Woo · Magento · BigCommerce · 65 more
8+ / 10
Meta EMQ guaranteed
in writing — keep working free until hit
2–4d
Build to live
accurate data flowing within 7 days
$0
Monthly fees, ever
one-time fixed price · you own the stack
400d
Cookie lifetime
max RFC 6265bis allows · 57× Safari ITP
9
Ad channels covered
Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X
95%+
Tracking accuracy
verified vs Stripe · GA4 · ad-platform reports
30 min
Free founder call
no SDR · no pitch deck · written remediation plan
Every figure above is either a commitment we put in writing or a countable fact. What your own setup is losing is not on this list, because we haven’t measured it yet — that happens on the call, against your own order records.
Real clients · real videos · real outcomes
Don’t take our word for it. Watch the receipts.
Founders, marketers, and agency owners describing the before-and-after of their Weave → Pinterest tracking rebuild — in their own words, on camera.
Why this join usually fails
The epik click identifier never reaches Weave
The single most common cause. A call carries no cookie. The join has to be made on the phone number, which means the identifier must already be attached to the number that was dialled.
Counting calls instead of patients
A call is not a booking. Wrong numbers, existing patients rescheduling, sales calls and hang-ups all land in the same total, and optimizing toward call volume buys you more of all of them.
The save-now-buy-later gap
Pinterest's whole behaviour model is saving something for later. A share of the revenue it genuinely drives arrives months after the click and outside any attribution window, and no build changes that. Say it before anyone sets a target.
Nothing reconciles afterwards
An upload that succeeds is not an upload that matched. Pinterest Ads Manager reports events received and their match status. A successful API call is not a matched conversion — reconcile Pinterest's reported conversions against your own records for the same window and expect a structural gap from the save-then-buy delay.
Architecture
How Weave and Pinterest actually connect
Two systems that know nothing about each other. Everything below exists to give them one shared reference.
Step 1
Weave holds the truth
In dental and optometry the phone is still the dominant booking channel. A measurement plan that only counts online bookings is measuring the minority of the business.
Step 2
Pinterest needs a click to match
Pinterest matches server events using the click identifier where present and hashed customer information otherwise. Confirm current endpoint and field names against Pinterest's own documentation — its Conversions API has been through more than one revision.
Step 3
The identifier is the bridge
The epik click identifier, captured at the visit and carried into the Weave call or booking. Without it there is nothing to join on and no tool fixes that.
Step 4
The event source decides reliability
Send attended appointments as a plain count. Call duration is a useful internal quality signal and is not a conversion.
Step 5
Deduplication at the destination
Pinterest deduplicates on event_id, so the tag and the server event must carry the same value for the same conversion. Pinterest volumes are often low enough that a doubling reads as a good week rather than a bug, which is why this needs testing deliberately rather than assuming.
Diagnose it honestly
Working vs. broken, side by side
Both states look identical from the Pinterest dashboard, which is why this runs for months before anyone notices.
Normal — not a fault
The epik click identifier present on the booking
Visible on the record itself in Weave, not merely captured somewhere on the site.
Sent from your practice management system
Server-side, so it does not depend on the customer's browser still being there.
Deduplicated correctly
Pinterest deduplicates on event_id, so the tag and the server event must carry the same value for the same conversion. Pinterest volumes are often low enough that a doubling reads as a good week rather than a bug, which is why this needs testing deliberately rather than assuming.
Reconciles with the source
Pinterest's count and Weave's records agree within a few percent over a closed window.
Actually broken
The epik click identifier missing on most records
A call carries no cookie. The join has to be made on the phone number, which means the identifier must already be attached to the number that was dialled.
Sent from the browser
Anyone who closes the tab, blocks the script or converts without a page load is invisible. A call is not a booking. Wrong numbers, existing patients rescheduling, sales calls and hang-ups all land in the same total, and optimizing toward call volume buys you more of all of them.
Counted twice, or not at all
Pinterest's whole behaviour model is saving something for later. A share of the revenue it genuinely drives arrives months after the click and outside any attribution window, and no build changes that. Say it before anyone sets a target.
Nobody has reconciled it
The dashboard shows a number and no one has compared it to Weave. A wrong number that nobody checks is indistinguishable from a right one.
Diagnostic sequence
Diagnostic order
Each step rules out a class of cause. Run them in order and the last one usually has a single explanation standing.
- 1
Count bookings carrying the epik click identifier
The ceiling on everything else. Do this before debugging anything downstream.
- 2
Follow one real conversion end to end
From the ad click through Weave and into Pinterest.
- 3
Measure what share of calls become attended appointments
It is usually far lower than expected, and the ratio differs enormously by campaign.
- 4
Check the event delivery and match reporting in Pinterest Ads Manager
Not the API response code. A 200 means Pinterest accepted the payload, not that it matched it to a click.
- 5
Read the match rate, not the success message
Pinterest Ads Manager reports events received and their match status. A successful API call is not a matched conversion — reconcile Pinterest's reported conversions against your own records for the same window and expect a structural gap from the save-then-buy delay.
Source-of-truth validation
How it gets proven
Against Weave's own records, not against either platform's dashboard.
- The epik click identifier confirmed present on a live booking.
- A real conversion followed from click through Weave to Pinterest.
- Deduplication confirmed on a real conversion, and the attribution window your reporting uses stated explicitly.
- Attended appointments reconciled against imported conversions, with raw call volume reported separately.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later.
Straight talk
When you don't need this
Worth reading before paying anyone, including us.
- If Pinterest already reports conversions that reconcile against Weave's records within a few percent, this join is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred bookings and count how many carry the epik click identifier. Ten minutes, free, and it tells you whether any of this is worth doing.
- A practice that books almost entirely online does not need call tracking, and adding it introduces a PHI surface for no gain.
- If Pinterest is a small test line on your media plan, the Conversions API is more work than the signal is worth this quarter.
Who this is for
Honest about who we’re a fit for.
We don’t take every project. Here’s how to tell if we’re right for you.
You’re a great fit if…
- You run Weave → Pinterest (or are migrating to it)
- You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
- Your reported ROAS doesn’t match what your bank account is saying
- You want to own your tracking stack — no monthly SaaS fees forever
- You have 2–4 days to do this once and never think about it again
Skip us if…
- You spend less than $500/month on paid ads (browser pixel is fine)
- You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
- You need attribution modeling — we fix the data foundation, not multi-touch reports
- You want a 6-month enterprise consulting engagement (we ship in 4 days)
- You expect us to manage your ad accounts (we don’t — that’s a different service)
If you’re still unsure,book the call anyway— we’ll tell you straight whether we can help.
What working looks like
The epik click identifier on every booking
Server-sideCaptured before the conversion and stored where it survives.
Conversions arriving in Pinterest
8+ EMQConversions appear in Pinterest Ads Manager against the campaign, with the value you sent, and become usable for optimization.
Reconciled against the source
DedupedWeave's own records are the reference, not either dashboard.
What gets built
Identifier capture into Weave
Use dynamic number insertion so the number displayed carries the session, then persist the identifier against the patient record when the call converts.
Event source: your practice management system
Send attended appointments as a plain count. Call duration is a useful internal quality signal and is not a conversion.
Dispatch to Pinterest
Server events to the Pinterest Conversions API with the click identifier, hashed customer data and a matched event_id.
Reversals where they exist
Cancellations and no-shows reverse.
Pick the package that fits your ad spend
Fixed-fee, no surprises. If your ad spend is meaningful,server-side tracking is what we recommend— it’s the only setup that survives iOS, Safari ITP and ad blockers.
Browser-side starter
Wires the join and verifies it on a live conversion. Honest about its ceiling where the source can only be read from the browser.
- The join built and tested end to end
- Verified on a real conversion
- Reconciled against the source's own records
- Written handover
1st-party server-side
Save $18K–$120K over 5 years vs Triple Whale / Hyros
The join built server-side from the source's own records, so it does not depend on a browser being present when the conversion happens.
- Events sourced from the system of record, not the browser
- Identifier captured and persisted end to end
- Deduplicated at the destination
- Reversals wired where the source supports them
- 95%+ accuracy guaranteed in writing
Full 1st-party stack
Every destination fed from one place, plus monitoring so a broken join surfaces in days rather than at quarter end.
- Everything in 1st-party server-side
- All paid destinations from one container
- CRM and offline loop
- Refunds and cancellations reversed everywhere
- Monitoring per destination
Not sure which tier fits?Book a 30-min scoping call— we’ll tell you straight, no upsell pressure.
How it works
Built in 2–4 days. Accurate data within 7.
We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.
Kickoff + audit
30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.
Build the stack
Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.
QA + go-live
Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.
Verify accuracy
Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.
Got questions?
The honestanswers.
No buzzwords, no upsell. If we don’t know, we say so.
01Why aren't my Weave conversions showing in Pinterest?
Almost always because the epik click identifier never reached the Weave call or booking. A call carries no cookie. The join has to be made on the phone number, which means the identifier must already be attached to the number that was dialled. Measure coverage before debugging the dispatch.
02What identifier does Pinterest need?
The epik parameter, appended to your landing page URL and stored by the tag in the _epik cookie. Pinterest also matches on hashed email and phone. The complication is behavioural rather than technical: a Pin saved in October and acted on in December is completely normal, so a meaningful share of genuine Pinterest-driven revenue falls outside any click window and is structurally unattributable.
03Where should the event come from?
Your practice management system. Send attended appointments as a plain count. Call duration is a useful internal quality signal and is not a conversion.
04How do I know it worked?
Pinterest Ads Manager reports events received and their match status. A successful API call is not a matched conversion — reconcile Pinterest's reported conversions against your own records for the same window and expect a structural gap from the save-then-buy delay.
Still have questions?Book a 30-min call— bring them all.
The call
What happens on your free 30-min call
No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and yourWeave → Pinterest setup — we’ll work through it together.
Min 1–5
We get the lay of your store
What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.
Min 5–15
We audit your tracking live
Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.
Min 15–25
We map a fix
What needs rebuilding, what stays. The exact Weave → Pinterest setup we'd ship and what it would recover for you.
Min 25–30
Decide. Or don’t.
If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.
Get Weave and Pinterest joined properly
Book a free 30-minute call. We measure your identifier coverage live on your own account, and you leave with a written plan — including the option that you don't need us.
Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp
Using Weave for bookings? How Weave bookings get tracked end to end
95% tracking accuracy guarantee
Free 30-min consultation · from $400 · 1st-party server-side
95% guarantee · from $400
