The only sGTM-native ASP that delivers a unified fbc + em + ph CAPI payload. We rebuilt, from the design stage up, the measurement surface that legacy ASPs cannot structurally reach. Lift your entire conversion measurement infrastructure onto the server side — in one move.
Postback-based ASPs circulating in Japan are designed around a measurement protocol from the postback era. That design philosophy structurally cannot transmit the high-quality CAPI learning signals that Meta and TikTok's algorithms now require. This is not about which specific service is better — it's a generational gap in design philosophy.
Legacy ASPs predominantly send only the click identifier (fbc) via postback. Because they cannot include PII hashes like em and ph in the same request, Meta's algorithm is fundamentally starved of the information it needs to identify users.
ASP postbacks are architecturally designed to transmit via URL query parameters. SHA-256 hashes of PII (em, ph) are long and impractical in query strings. The nested user_data JSON structure that CAPI requires cannot be expressed in a postback.
When sending the same conversion to Meta / Google / Yahoo / TikTok / LINE, legacy ASPs manage each platform as a separate integration. With no unified deduplication key design, double-counting the same user across platforms remains a structural problem.
track-19DD is an ASP designed as sGTM-native. Where legacy ASPs bolted CAPI on afterward, we rebuilt the entire product from the server-side-first starting point — enabling implementations that are structurally out of reach for competitors.
For a single conversion event, sGTM bundles click identifiers (fbc/fbp), email (em), phone (ph), and external_id in one pass and sends them to Meta as a single request. This is structurally impossible to replicate with other ASPs.
When the same conversion fires through browser pixel, CAPI, and postback, ad dashboards drift away from reality — and Meta and TikTok's algorithms end up optimizing on flawed learning data. track-19DD stamps every event with a unified event_id, guaranteeing deduplication on the platform side. Your partners' revenue stands on numbers that are actually accurate.
As an official Stape Partner (Partner ID: bbmbgajd), we fully leverage Stape Store's reStore feature. User-entered em / ph / external_id are persisted server-side, then restored across every subsequent CAPI request — pushing EMQ to its ceiling.
We compare on feature presence, not vibes or impressions. The items below are the must-have functions that determine measurement quality in the CAPI era. This matrix is designed so you can take it directly into an internal approval document.
| // Feature | track-19DD | Legacy ASP A | Legacy ASP B |
|---|---|---|---|
| Unified fbc + em + ph CAPI payload unified CAPI in single request | Full | No | No |
| fbc transmission click identifier | Yes | Yes | Yes |
| em (hashed email) transmission SHA-256 email hash | Yes | Partial | No |
| ph (hashed phone) transmission SHA-256 phone hash | Yes | No | No |
| sGTM-native design server-side GTM native | Native | Not supported | Not supported |
| Stape Store / reStore server-side user enrich | Partner | No | No |
| LIFF × fbc bridging LINE webview fbc bridge | Yes | No | No |
| Yahoo CAPI (_ly_c / _ly_rt) Yahoo server-side conv | Yes | Postback only | Postback only |
| Multi-stage MCV tracking micro-conversion funnel | Configurable | Final CV only | Final CV only |
| Unified dedup key (event_id) unified dedup key | Unified | Per platform | Per platform |
| EMQ average score Event Match Quality avg. | 9.2 / 10 | 6.0 / 10 | 5.5 / 10 |
| BigQuery integration raw event log export | Standard | Optional | No |
| BOTCHAN / ecforce integration chatbot + cart CV track | Implemented | Custom build | Custom build |
| Meta CAPI Gateway equivalent first-party CAPI infra | Equivalent | N/A | N/A |
Every event from the web front-end, LIFF, and chatbot layer flows into a single entry point: sGTM on Stape (the track-19DD container). User data is enriched via Stape Store, then simultaneously delivered to five ad platforms via CAPI. Raw-log export to BigQuery is standard.
Three representative implementation patterns — each difficult or impossible to realize on legacy ASPs, and only made possible by track-19DD's sGTM-native architecture. All three are in continuous production.
During the period when Yahoo's official sGTM template was unreleased, we built a custom implementation with Stape's JSON HTTP request tag. The _ly_c / _ly_rt cookies are persisted server-side, feeding every conversion — including those lost in the postback path — back into Yahoo's delivery algorithm.
For an environment where the same CV fired multiple times across browser Pixel, CAPI, and postback, we implemented a design that stamps every event with a unified event_id. Meta's dashboard CV count now matches reality, and the CPA inflation caused by flawed learning data is resolved. Algorithm learning accuracy improved dramatically.
Micro-conversions fired at each step of BOTCHAN / ecforce forms (email entry, phone entry, cart reach, payment complete) are sent to Meta as independent CAPI events. By granularizing the optimization target, learning speed improves dramatically.
track-19DD onboarding runs in parallel with your current measurement stack — we don't turn anything off. The decision to cut over happens only after you've verified data quality in parallel operation, minimizing migration risk.
Reach out via the contact form or directly. We'll hear out your current measurement configuration.
We finalize CAPI requirements, LIFF integration scope, and MCV design — and present the Stape + sGTM container blueprint.
Build the sGTM container, test CAPI delivery, and run in parallel with the existing ASP to verify data quality.
Post-cutover, we continuously optimize via the dashboard and weekly reports. Stape operations and maintenance are included.
track-19DD uses sliding pricing based on monthly CAPI event volume. It's a full-service contract including onboarding consulting, sGTM build, and ongoing operations. Specific quotes are provided after we hear out your current delivery volume, required platform count, and measurement requirements.
Integrated service covering initial build, sGTM operations, CAPI implementation, dashboard access, and weekly reporting. We design the optimal plan based on current delivery volume, required platform count, and custom requirements.
Product details, onboarding conditions, and pricing bands for track-19DD are shared exclusively through direct inquiry. If you're interested in what we're building, please reach out via the form below. We reply within 2 business days.