Agence marketing B2B
Meridian Digital
Formulaires, pages merci et discipline CRM
Les formulaires de Meridian fonctionnaient—jusqu’à ce que non : leads dupliqués, IDs campagne manquantes et pages merci qui cassaient le tracking sur parcours assistés. Cette phase a resserré la plomberie pour que le marketing fasse confiance aux chiffres du pipeline.
Contexte
Sales complained about duplicate records after events and webinars; marketing saw different numbers than CRM dashboards.
Consent and region rules added complexity: not every field should go to every automation.
Contraintes
Stay within the CRM’s public APIs—no shadow databases.
Preserve user-facing copy tone; legal reviewed disclaimers that couldn’t move casually.
Recherche
We traced a sample of leads end-to-end and found timing issues—webhooks arriving out of order—and mapping gaps where UTM fields didn’t align to CRM picklists.
We reviewed error logs for silent failures (the worst kind).
Approche
Server-side validation with structured error responses; client mirrors for UX but server wins.
Idempotent webhook handling and dead-letter visibility so ops can retry without guessing.
Livraison
Thank-you pages are real routes with consistent event hooks; assisted conversions become measurable without hacks.
Documentation includes field dictionaries for CRM admins—boring, essential.
Résultats (indicatifs)
Duplicate lead noise dropped after idempotency keys and smarter dedupe rules.
Reporting between ads and CRM converged enough for weekly standups to trust the trend lines.
Stack & integrations
- CRM REST API
- Server validation
- Webhook retries
- GA4 events