Asynchronous boundary updates

When an admin/postal boundary source updates, ad platforms and the advertiser's own crosswalk do not necessarily update on the same date; targeting and reporting can briefly use different boundary vintages for the same campaign.

Class

Case to account for

Affects

2 conversions

Detection

Compare the boundary vintage timestamp used for targeting against the vintage used for the reporting join; flag mismatches.

Mitigation

Pin and log the boundary vintage used at both targeting time and reporting time

Re-run the crosswalk and flag affected flights whenever a platform's boundary source updates mid-campaign

Affected conversions

Admin polygonsH3 (weighted crosswalk)

OPEN

H3platform-native IDs

OPEN