Conversion APIs · Destination connector
Floodlight Conversions API — Data Manager ELT Connector
Extract delivers approved, modeled business data to Floodlight Conversions API — Data Manager. Teams use it to send validated, consent-aware conversion events for downstream measurement and keep those downstream actions current on a flexible schedule.
View setup guide
Use cases
What teams use this connector for
Server-side conversion delivery
Use Extract Reverse ETL to send validated conversion events to Floodlight Conversions API — Data Manager.
Event enrichment
Add approved order, customer, or campaign attributes to modeled events before delivering them to Floodlight Conversions API — Data Manager.
Conversion reconciliation
Use governed event models to keep Floodlight Conversions API — Data Manager conversion reporting aligned with internal business definitions.
Consent-aware event workflows
Apply consent and eligibility rules before sending modeled conversion records to Floodlight Conversions API — Data Manager.
Governed scheduled delivery
Keep Floodlight Conversions API — Data Manager supplied every 15 minutes, hourly, daily, or on a custom schedule using data models that teams can test and approve.
Connector data
Data accepted by this destination
Receives mapped Floodlight conversion events for the selected advertiser and configuration.
Why Extract
Why Extract for Floodlight Conversions API — Data Manager
- Rust-native performanceDeliver approved records to Floodlight Conversions API — Data Manager with Rust-native data movement on a schedule that matches the operational workflow.
- Full run transparencyInspect Floodlight Conversions API — Data Manager delivery execution, timing, and failures in Extract's run-level logs.
- ELT + Reverse ETL in oneBuild governed models from inbound data, then use Extract Reverse ETL to activate the approved records in Floodlight Conversions API — Data Manager.
FAQ
Frequently asked questions
How does Extract handle incremental and full Floodlight Conversions API — Data Manager deliveries?
An incremental delivery processes only new or changed data since a stored checkpoint or new date partition, while a full delivery processes the complete selected dataset or date range again. By avoiding repeated processing and writes for the full dataset, incremental deliverys can reduce destination database updates and warehouse compute costs. Not applicable to destinations; uploads source conversion events. Extract records run details so teams can verify each delivery.
Can I backfill historical Floodlight Conversions API — Data Manager data with Extract?
Historical coverage for Floodlight Conversions API — Data Manager: Uploads supplied historical events; acceptance depends on Google eligibility and limits. Use the setup guide and run details to confirm the available source records and selected settings.
How should teams prepare data for Floodlight Conversions API — Data Manager?
Prepare and validate the modeled records before delivery, including any eligibility, consent, or suppression rules required by the workflow. Then use the Floodlight Conversions API — Data Manager setup guide and Extract's run-level logs to validate each delivery.
How often can Extract deliver data to Floodlight Conversions API — Data Manager?
Extract supports schedules every 15 minutes, hourly, daily, or on a custom cadence. Teams can choose a frequency that matches routine reporting, time-sensitive monitoring, or operational activation needs.
What does the Floodlight Conversions API — Data Manager data model look like in the destination?
Floodlight Conversions API — Data Manager receives the approved modeled records selected in the connection. The destination shape follows that validated model; use the setup guide to confirm any connector-specific field requirements.