Integration guide
How internal systems connect to RTSFZH Ads for Google Ads delivery and how data should flow. Adjust hostnames and regions to match your deployment.
Reference architecture
Google Ads (OAuth/API) → RTSFZH Ads services → approved export targets (warehouse, BI, object storage). Avoid copying full exports to laptops; use VPN and managed workstations where policy requires it.
Exports
- Scheduled CSV/Parquet: configure in the admin UI (staging first), then promote with change ticket.
- On-demand download: role-gated; row limits apply per tier.
- Checksum: each batch includes
manifest.jsonwith SHA-256 for integrity verification in pipelines.
Webhooks
Outbound events include job.completed, rule.triggered, and export.ready. Retry with exponential backoff; verify signatures using the shared secret in the internal secrets store.
Failure modes
| Symptom | First check |
|---|---|
| 401 on API | Token expiry; rotate via ops runbook |
| Partial export | Rate limit; split date range |
| Webhook 5xx | Endpoint SLA; dead-letter queue in monitoring |