Marketing analytics across Belfast and Ireland

What to take away

UK and EU data flows across the Irish border from Belfast

A Belfast team running campaigns in Ireland is moving personal data between two legal regimes. The UK runs on UK GDPR and the Data Protection Act 2018, with the ICO as regulator. Ireland runs on EU GDPR, with the Data Protection Commission in Dublin. The rules rhyme, but they are not the same text.

That matters most for identifiers. A hashed email collected in Dublin and matched to a Belfast CRM record is a transfer of personal data, even if the hash never leaves your warehouse. Device identifiers and IP addresses count too.

If you are mapping personal data and device tracking, row by row, the jurisdiction of collection is a field you need, not an afterthought.

Northern Ireland's position is unusual. The Northern Ireland Act 1998 set the constitutional baseline for devolved governance, and data protection has since been shaped by the UK's post-Brexit settlement rather than by Brussels.

In practice, a Belfast analyst can lawfully process data under UK rules while a Dublin colleague processing the same customer must follow EU rules.

Practical consequence: your tag management, consent banner and retention schedule need to know which side of the border a session started on. Most analytics stacks do not capture that by default. Add a country field at collection, and keep the consent record with it.

A consent management platform such as OneTrust and a tag manager such as Google Tag Manager can pass consent status and jurisdiction to permitted tags. Configure them so the consent record stays associated with the session.

Receiving personal information from the EEA and what it means here

When data travels from Ireland into the UK, the UK is the recipient. The ICO's guidance on receiving personal information from the EEA sets out what a UK controller should have in place. It is short, and it is the document your legal reviewer will ask for.

The core expectation is that the transfer rests on a recognised mechanism, and that you can show what it is. For most Belfast marketing teams that means either an adequacy-based route or standard contractual clauses, depending on the data and the exporter.

For an Ireland-to-UK transfer, record whether the European Commission's adequacy decision for the UK covers the data flow. The UK International Data Transfer Agreement (IDTA), the UK Addendum to the EU Standard Contractual Clauses and a transfer risk assessment (TRA) are relevant to restricted transfers from the UK to a third country; they do not replace documenting the incoming route.

The ICO also expects you to record the transfer, review it, and give individuals clear information about it.

Three things go wrong most often. First, the importer signs the clauses but nobody updates the privacy notice. Second, the data flows through a processor in a third country without a fresh assessment. Third, retention is set by the exporter and ignored by the importer. Each is fixable with a line in a register.

If you are negotiating the paperwork with an agency or platform, attribution contracts, clause by clause is a useful companion. It forces the data role question early, which is where most cross-border disputes actually start.

Currency handling and VAT place of supply for cross-border campaigns

Currency handling is the quieter problem. A campaign that spends in euros and reports in sterling will show a different return on ad spend depending on the rate you pick.

Pick one convention and write it down: either a fixed monthly rate from a published source, such as HMRC's monthly exchange rates, or the daily rate at transaction time. Record the source and period, apply it consistently within a report, and ask finance to confirm whether the same convention is suitable for tax reporting.

For business-to-business services, the place-of-supply rules in the VAT Act 1994 and HMRC's VAT Notice 741A, Place of supply of services, generally put the supply where the customer belongs. The EU VAT Directive applies the corresponding general rule in Ireland. A Belfast agency billing an Irish business client will generally not charge UK VAT, with the client accounting for Irish VAT under the reverse charge, subject to the service and customer status.

This is where the reporting gets interesting. VAT place of supply affects what you invoice, not what you measure, but the two get tangled when platform fees, media spend and management fees sit on one line. Split them. Media spend is usually a disbursement; your fee is the service.

HMRC guidance on cross-border services is a starting point. VAT Notice 741A, Place of supply of services, is the detailed HMRC reference for place of supply; check current HMRC registration guidance separately. Keep the invoices and the attribution reports aligned by period, or your finance team will reconcile two different versions of the same campaign.

Overlapping campaigns measuring audiences on both sides of the border

Belfast sits within easy reach of Dublin, Newry and Dundalk, and audiences do not respect the border. A single paid social campaign can reach users in both jurisdictions within a few miles. If your reporting splits them by country, you will see two smaller, noisier datasets instead of one useful one.

There is a middle path. Keep the campaign unified for delivery, but tag every session with a jurisdiction attribute. Then report both ways: a combined view for performance, and a split view for compliance and budget. This avoids the common failure where a strong Irish result is buried inside a weak UK average.

The same person can appear as a UK user on one device and an Irish user on another, particularly with shared accounts. Deduplicate on a stable, consented first-party customer ID before you assign credit, or your conversion counts will exceed your sales.

Choose one attribution model, such as last-click or data-driven attribution, and apply it consistently to combined and jurisdiction-split reports. Do not add the results from those two views together.

When you are comparing tooling for this, comparing attribution pricing structures on identical fields is a practical way to see what each vendor charges for cross-border segmentation before you commit.

Setting up attribution when one audience spans two jurisdictions

Use the same jurisdiction field throughout the analytics platform. For example, in Google Analytics 4 (GA4) register it as a session-scoped custom dimension; in Adobe Analytics map it to an eVar; in HubSpot store it in a custom property.

Consider a Belfast retailer that sells online in both Northern Ireland and the Republic, spends in euros on Meta and sterling on Google, and reports in sterling. Belfast retailer

Step one: Map where data is collected and attach the jurisdiction and consent record to each session.

Step two: Pass the jurisdiction field through your tag manager and analytics platform, using the same field definition in each system.

Step three: Record the transfer route for EEA data and review any onward transfers separately.

Step four: Set one reporting currency and FX convention; keep media spend, platform fees and your service fee distinguishable in reports and invoices.

Step five: Deduplicate on a stable, consented first-party customer ID, then report both combined and jurisdiction-split results using the same attribution model.

Step five is the one teams skip. Cross-border attribution fails quietly when refunds, currency and jurisdiction are handled in three different places.

Before you sign anything, investigating an attribution vendor before procurement is worth the hour. Ask how they handle jurisdiction fields, FX conventions and EEA transfers in writing. A vendor that cannot answer all three will cost you more in reconciliation than it saves in licence fees.

Common questions