Sonar Meta EMQ Table
sonar_meta_emq_table
The Sonar Meta EMQ table contains metadata about Sonar-enriched events sent to Meta via the Conversions API (CAPI), including event details and match quality indicators. Querying this table can help evaluate data enrichment effectiveness, track identifier coverage, and improve Event Match Quality scores.
Note
event_dateis a required field for queries on this table.
Dimensions
Dimensions are immutable properties that can be used for grouping data.
Title | ID | Type | Description |
|---|---|---|---|
Event Date |
| date | The date the Sonar event occurred. Based on the shop time zone at the moment of the event (or the user time zone, if no sales platform is connected). |
Event Day |
| date | The day on which the event occurred. Derived from |
Event Week |
| date | The Sunday of the week during which the event occurred. Derived from |
Event Month |
| date | The month during which the event occurred. Derived from |
Event Quarter |
| date | The first month of the quarter during which the event occurred. Derived from |
Event Year |
| date | The year during which the event occurred. Derived from |
App Parameter Coverage |
| JSON | An array of parameter coverage metrics for app-based custom attribution events. Each entry contains: |
Data Freshness |
| string | Data freshness indicates the delay between the time the event occurred and when we received it. Values can be "real_time", "hourly", "daily", etc. Events sent with a delay may impact how effectively your ads can be delivered to the right audiences. Stored as LowCardinality(String) with default empty string. |
Diagnostics |
| JSON | An array of diagnostic issues identified for custom attribution (passback) events. Each diagnostic contains: Example diagnostics_type values: |
Event Name |
| string | The name of the Sonar event. Example values: |
Match Quality Identifiers |
| JSON | A list of key-value pairs, where each pair represents an identifier used for match quality assessment. Each identifier has a name (e.g., |
Web Parameter Coverage |
| JSON | An array of parameter coverage metrics for web-based custom attribution events. Each entry contains: |
Measures
Measures are numeric fields that can be aggregated and/or combined to calculate new metrics.
| Title | ID | Type | Description |
|---|---|---|---|
| Additional Conversions Reported (ACR) | acr | numeric | Additional Conversions Reported (ACR) is a metric that helps you understand how much your business benefits from using the Conversions API alongside the Meta Pixel. It can help you determine if you can improve your Conversions API setup to measure more reported conversions. More reported conversions can help you decrease your cost per result and show your ads to people that find them relevant. |
| Event Coverage | event_coverage | numeric | Event Coverage indicates the percentage of events that are successfully tracked and attributed. This metric helps evaluate how effectively events are being captured and processed through the Conversions API integration. |
| Event Potential ACR Increase | event_potential_aly_acr_increase | numeric | Additional Conversions Reported (ACR) for Conversions API Event is a metric that estimates how many conversions (for example, purchases or link clicks) are measured as a result of an advertiser's Conversions API setup. For Meta Pixels not connected to the Conversions API, this metric estimates the impact a Conversions API integration may have. Higher values indicate greater potential for conversion rate improvement through better data quality. |
| Match Quality Score | match_quality_score | numeric | A numeric score (out of 10) representing the overall quality of the match based on available user identifiers. Higher scores indicate better match confidence. |
Updated 19 days ago