LLupe Docs lupedata.com ↗
Browse all guides
Guides › Get Started
Security & access

Minimum Access Framework

How Lupe and TDS ask for only the access needed to set up and test your first-party tracking, and nothing more.

Client onboarding guide ◷ Under 5 minutes 0 of 4 steps done
Updated Nov 3, 2026

Minimum necessary access is our data minimisation framework. We ask only for the access needed to configure and test your first-party setup. In practice, that means being able to see the events your website sends to each platform.

Your part
  • Share only the access listed for each platform, from your own account
  • Check our partner details against each request
  • Remove our access whenever you like
Our part
  • Connect your server container and check that events arrive at each platform
  • Ask for admin access only if you request support with a specific task
  • Show you an aggregated, anonymised analytical view

Before you start

  • Understand that you retain admin rights on each platform you are setting up with us. You stay in control throughout.
  • Never give passwords or login information to anybody - we will never ask for these.
  • Prepare a list of the platforms you want to connect (for example Shopify, Meta or TikTok).

Your steps

1
Your part

Open the guide for each platform that is relevant to your setup

Each platform has its own step-by-step guide:

2
Your part

Check our partner details

When you see a request or search for us in your account, compare it with the partner details below. Only continue if they match.

3
Your part

Share only the access we list

Give us the access shown in the table below, on the single dataset, pixel, property or ad account you choose. Don't share anything broader.

We don't ask for admin access by default. We only ask for it if you've requested our support with a specific task or a troubleshooting session.

4
Your part

Remove our access when you no longer need us

You can remove our access at any time. Every platform guide shows where to see and remove it.

What we ask for

PlatformWhat we ask forWhat we don't access
ShopifyCollaborator access with four permission areasOrders, products, customer lists, payments or staff accounts
WordPressNo login: you install the Stape plugin yourselfOrders, customers, payments, pages and theme
Meta✓ Full control of one datasetOther datasets, ad accounts, Pages, Instagram, catalogues, billing, portfolio settings
TikTok✓ Edit pixels on one pixelOther pixels, advertiser accounts, catalogs, shops, billing, Business Center settings
Google Ads✗ No access. You approve a GA4 link and send us a conversion ID and labelYour whole Google Ads account: campaigns, budgets, spend, billing and leads
Google Analytics 4✓ Editor on one propertyOther properties, users and permissions, account settings
LinkedIn✓ Campaign Manager on one ad accountOther ad accounts, company pages, billing
Pinterest✓ Analyst on one ad accountCampaigns, billing, profiles, catalogs, audiences
ChatGPT ads (OpenAI)✓ Member on one advertising accountAccount administration, other advertising accounts, ChatGPT workspaces

Shopify

Shopify areaPermissionWhy we need it
Store settingsManage settingsGives access to Customer privacy, so we can configure Shopify's default cookie banner in consideration of your chosen consent platform.
Store settingsView customer events; Manage and add custom pixelsLets us configure checkout events to your server-side container.
Apps and channelsManage and install apps and channelsLets us configure the Stape app once you've installed it.
Online storeThemes: edit codeLets us switch on the Stape app embed, configure your consent banner script with the theme, and isolate the location of old, non-compliant or conflicting tracking scripts.

Meta

AreaAccessWhat that means
Your chosen dataset✓ Full controlView incoming events, run test events, check deduplication and event quality, adjust advanced matching and event settings, and connect your server container (Conversions API).
Other datasets or pixels✗ NoOnly the one dataset you assign.
Ad accounts✗ NoNo customer or lead information, campaign access, budgets or ad performance.
Facebook Pages and Instagram✗ NoNo posting, messages or community management.
Catalogues✗ NoNo changes to products or product sets.
Billing and payments✗ NoNo payment methods, invoices, spend or credit lines.
Business portfolio settings✗ NoNo access to your people, other assets or partners.

TikTok

AreaAccessWhat that means
Your chosen pixel✓ Edit pixelsView incoming events, run test events, check deduplication and event quality, and connect your server container (Events API).
Other pixels✗ NoOnly the one pixel you share.
Advertiser (ad) accounts✗ NoNo customer or lead information, campaign access, budgets or ad performance.
Catalogs and shops✗ NoNo changes to products or shops.
Billing and payments✗ NoNo payment methods, invoices or spend.
Business Center settings✗ NoNo access to your members, other assets or partners.

Our partner details

Check these against any request you see in your accounts.

PlatformPartner nameID
MetaLupe \TDS
TikTokLupe \TDS
Google Ads–No access needed: you send a conversion ID and label
Google Analytics 4, ChatGPT adsLupe analyticsanalytics@lupedata.com
LinkedIn, PinterestLupe \TDS
ShopifyLupe Data \TDS

What happens next

  • We use the access you granted to connect your server container.
  • We check that the events arriving at each platform are correct, using test events.
  • We show you an aggregated, anonymised analytical view in Lupe.
  • We only ask for admin access if you request support with a specific task or troubleshooting session.

Good to know

  • You stay in control. Lupe and TDS never own or control your datasets or ad accounts. Lupe is a dashboard layer: all processing happens in accounts that you own.
  • No ad account, order or financial data. We don't get access to your campaigns and budgets, order information, customer lists, billing or financial information.
  • Aggregated views only. Lupe doesn't store or use your platform data, except to show you an aggregated and anonymised analytical view.
  • Test events. When we run test events, we see the event details the platform shows for that test traffic. Personal details such as email addresses are hashed (scrambled) before they reach Meta or TikTok. We don't download or keep any of your event data.
  • Legal terms. These permissions are set out in Annex D of our Data processing agreement. See also our Privacy policy.