Please see the information below for how to share ad platform data with Paramark. The channels covered in this document are the most common channels we connect to, but not an all-inclusive list. We'll provide additional instructions during onboarding for any not listed here.

Channels are organized into two groups:

• Ad Platform Connections - direct API or account access where no manual file uploads are required

• Manual / Offline Channels - shared via spreadsheet to your Paramark Google Drive folder

Ad Platform Connections

For these channels, we can either pull the data directly from the API (requiring an API key shared to Paramark) or via platform account access.

Amazon Ads

• If your Amazon advertising is managed by an agency or partner, please ask them to grant Paramark read access to the relevant Amazon Ads account(s).

• If direct Amazon Ads access is not possible, ask the agency or partner to set up a recurring Amazon spend report for Paramark instead. Include the fields or values Paramark needs for the workstream, and confirm whether the report should cover DMA-level spend, account-level delivery, or both.

• If account access is blocked, a historical or recurring export of daily spend and impressions by campaign is an acceptable alternative for Amazon Ads. The most useful file includes date, campaign name, spend, impressions, and the available history range. If a campaign-level impressions export is available but account access is not, send that file rather than waiting for direct platform permissions.

• If Amazon Marketing Cloud (AMC) or another Amazon reporting workflow is what you have available, a recurring export with at minimum date, campaign, and impressions is also acceptable. If available, include spend, brand or marketplace, and any notes about whether the file covers Sponsored Ads, Amazon DSP, or both.

• Please share the Amazon Ads account name(s) or account ID(s) that should be included, and specify whether access is needed for Sponsored Ads, Amazon DSP, or both.

• If you use multiple marketplaces, brands, or legacy Amazon ad accounts, include all active and recent accounts that should be part of the analysis.

Apple Search Ads

• Please follow instructions here to give us access to your whole account:

  • Name: Pranav Piyush

  • Apple ID: pranav-apple-search-ads@paramark.com

  • Role: API Account Manager

Bing

• Please add nicole@paramark.com to your Microsoft Ads Account as Analyst

GA4

• Please add nicole@paramark.com as an Administrator or equivalent admin-level user on the relevant GA4 property so Paramark can complete the connection.

• When you share access, please confirm which GA4 property or properties should be included if your team manages more than one brand, region, or website property.

• If you also use Google Search Console, please share that property separately so Paramark can compare paid and organic traffic trends where relevant.

ChatGPT Ads

• Please add your Paramark contact as a user on the relevant ChatGPT ads account with access to the full account or workspace needed for reporting.

• When you share access, confirm which ChatGPT ads account(s) should be included if your team manages more than one brand, region, or business unit.

• If you have older or inactive ChatGPT ad accounts that should still be included in historical reporting, send those account names as well so Paramark can confirm coverage.

• If a platform invitation has already been sent, let your Paramark contact know once access is active so the team can validate the connection and include the spend in the next refresh.

Google

• Share your Google Ad Account IDs (customer IDs) with Paramark and we will send you a request to link your Ads account from our Manager account.

• If your team uses a Google Ads manager account or team workspace already, you do not need to create a separate Paramark workspace first. Sending the relevant account ID is enough for us to request access, and your team can then approve that request inside Google Ads.

• If you're not sure which Google Ads account(s) should be shared, include the active account names and IDs for each brand, region, or business unit you want included.

• If you're running a geo-based incrementality test on YouTube, Search, Demand Gen, PMax, or another Google Ads campaign, we may also ask for a manual geo-resolved delivery export. In that case, please share a file with daily data by geography (state, DMA, or the geo level used in the test) that includes at minimum date, geography, campaign or test cell, spend, impressions, and clicks.

Google Search Console

• Please add nicole@paramark.com as a Restricted User (read-only access) on the relevant Google Search Console property.

• Restricted User access is usually sufficient for Paramark to review organic search performance; admin-level access is not required.

• When you share access, please confirm which Search Console property or properties should be included if your team manages multiple domains, subdomains, or regional sites.

• If you are also sharing GA4, please grant that access separately because Google Search Console and GA4 permissions are managed independently.

OpenAI / ChatGPT Ads

• If you are advertising on ChatGPT, please add your Paramark contact to the relevant OpenAI / ChatGPT ads account with access that allows campaign performance reporting to be reviewed.

• When you share access, please confirm which ads account should be included if your team manages multiple accounts, brands, or regions.

• If direct account access is not possible, ask your OpenAI / ChatGPT ads contact whether a recurring performance export can be shared with Paramark instead, including at minimum date, campaign, spend, impressions, and clicks.

Impact (Affiliates)

• In your Impact account, navigate to Settings.

• In the Technical section, select API Access

• Create or use an existing read-only token., share the account SID and auth token with Paramark

Adtraction (Affiliates)

• If you can export daily performance data from Adtraction, share a file with at minimum date, campaign or program name, impressions (if available), clicks, conversions, and spend or commission.

• If impressions were only enabled or backfilled starting partway through the history, still share the full export you have and note the exact date impressions begin. Earlier rows can still be useful with the other available metrics.

• If Adtraction cannot provide impression history for the full period, send the available date range anyway and flag the gap so Paramark can decide whether to use spend or another delivery metric for the earlier period.

• If a longer historical export is available only through a manual platform download, confirm the available start date first and only backfill farther if your Paramark team asks for it.

• Upload the file to your Paramark Google Drive folder or share it with your onboarding contact using the agreed handoff method.

Integrate

• Please contact the Integrate support team (support@integrate.com) for an API Key, Provide your API Key and Organization ID to Paramark.

Klaviyo

• In Klaviyo, go to Settings → Account → API Keys.

• Click Create Private API Key and share the key with Paramark on Slack.

• Read-only scopes are sufficient.

LinkedIn

• Please follow instructions here to share with Paramark

• Paramark's business ID in Linkedin is 7220739625709883392

Meta

• Please add Paramark as a partner in the Meta Business Suite.

• Paramark's Business ID is 213703414560125

• Assign all the ad accounts, Facebook pages, and Instagram accounts that are active now or have been active in the past 3 years.

• If your business has changed ad accounts over time (for example by country, brand, agency, or legal entity), send Paramark a list of the currently active account and any previous Meta ad accounts that should be included, ideally with account names and IDs.

• Full instructions here

Meta - Instagram

• For Instagram Account Insights (organic), please ensure

  • The Instagram account is a business account.

  • Instagram account is connected to your Facebook Page 

  • You've given Paramark access to the Facebook Page with the Analyst role.

  • Full instructions here

MNTN

• Log in to your MNTN account.

• In the top right corner of the page, click your account name, and then select My Account.

• On the navigation menu, click API.

• Copy the reporting API key and share with Paramark on Slack.

Pinterest

• In your Pinterest Business Manager, go to Business Access and invite Paramark as a partner.

• Grant Paramark Analyst access to your active ad account(s).

• Share your Pinterest Advertiser ID with Paramark on Slack.

Podscribe

• In Podscribe, go to Account Settings → API.

• Generate an API key and share it with Paramark on Slack.

• We'll pull daily campaign performance data (date, campaign, media type, impressions, spend) directly from the API — no manual file uploads needed.

Profound

• Add nicole@paramark.com to pull reports

Quora

• Request API crednetial from ads-api-help@quora.com, by providing them with redirect URL: https://fivetran.com/integrations/quora_ads/oauth2/return, your Quora username/information, a name for your application such as "Paramark share". Once this is created, login and navigate to https://www.quora.com/ads/oauth_client_data and share the client ID and secret with Paramark via slack.

Reddit

• Please add nicole@paramark.com as a member to Reddit business account and then as an Analyst to your Reddit Ad Account(s).

Snap

• In your Business Manager, click on Shared

• Share all assets with maximum permission with Paramark's organization ID: 6ae25975-009a-4c66-8b97-bb05e98e5967

Taboola

• Please reach out to your Taboola Account Manager to provide you with an API client ID and client.

• Provide the client ID and secret to Paramark.

TikTok

• Please follow instructions here to give us access as Ad account Analyst

• Our business ID is 7304086267753594881

Twitter / X

• Please add nicole@paramark.com as an Analyst to your Twitter / X Ads account.

StackAdapt

• In StackAdapt, go to Account Settings → API Integration.

• Generate an API key and share it with Paramark on Slack.

• If you don't see the API Integration option, contact your StackAdapt account manager to enable it.

• If API access is not available, you can instead set up a recurring StackAdapt performance report to send to Paramark. Use a recurring report that includes at minimum date or month, account or campaign name, spend, impressions, clicks, and conversions, and share it on the cadence your Paramark team requests. If the file is delivered as a temporary download link, please forward it promptly since some StackAdapt report links expire after 24 hours.

Universal Ads

• If you want Paramark to pull daily reporting from your Universal Ads account, invite nick@paramark.com as a team member on the relevant ad account.

• Follow Universal Ads' Invite and Manage Team Members flow to send the invitation from your account settings or team-members page.

• If your organization manages multiple ad accounts or workspaces, confirm which account should be shared so Paramark can validate the correct reporting connection.

• After the invitation is sent, let your Paramark contact know so the team can confirm access and start using the account for reporting.

YouTube (Organic)

• YouTube Organic data is shared via a manual export from YouTube Studio rather than a direct API connection.

• If the person coordinating with Paramark does not already have access to YouTube Studio analytics, please have a channel owner or admin grant the needed permissions first so they can open Advanced mode and export the report.

• Go to YouTube Studio → Advanced mode (top right) → set metric to Views by Date → filter traffic source to exclude Advertising → export as CSV using the Totals tab.

• Share the CSV file in your Paramark Google Drive folder. We'll provide the folder link during onboarding.

• We request this export periodically — your onboarding team will let you know the cadence.

Manual / Offline Channels

For the channels below, data is shared via CSV or spreadsheet upload to a shared Google Drive folder Paramark provides during onboarding. When uploading files, please follow these formatting rules:

If you're sharing a Google Sheet, Google Doc, Google Slides file, or uploading files to a Paramark Google Drive folder: you may receive an automated Google email such as "Spreadsheet shared with you," "Presentation shared with you," or a folder-sharing invitation. Those emails are expected when a customer or Paramark teammate shares the working file or folder with you.

• Make sure the right Paramark contact has Editor access if they need to update or normalize the file.

• If your company blocks sharing with external domains, ask your admin to allow sharing with @paramark.com collaborators or send the file as CSV using the agreed secure handoff method instead.

• Use clear file or tab names (for example, ToF Data) so Paramark can quickly identify what each shared spreadsheet contains.

Note: Manual / offline channels such as podcasts and newsletters may be ingested upstream before they appear in downstream geo/device reporting tables. If a channel is missing from a geo/device mart, it may still exist in an upstream spend table or manual input while geographic allocation logic is being finalized.

• One row per date (daily granularity preferred; weekly is acceptable if daily isn't available)

• Date format: YYYY-MM-DD

• Numeric values with no symbols (e.g., 1000.50 not $1,000.50)

• No "Total" or "Grand Total" summary rows

• Keep column names consistent across every upload

Podcast / Audio (Acast, Spotify Podcasts, iHeart, etc.)

• If your podcast buys are managed by an agency, ask them for a daily campaign performance export with the following fields: date, show or campaign name, channel (e.g., "Acast"), impressions or downloads, spend.

• If the platform provides a direct export (e.g., Spotify for Podcasters), export as CSV and upload to your Paramark Google Drive folder.

• Weekly granularity is acceptable if daily isn't available from your agency.

• If you're setting up a streaming audio or podcast incrementality test, share the planned vendor or platform (for example Spotify), the test timing, the geo or audience split if one exists, and the primary outcome you're measuring so Paramark can line up the delivery data with the experiment design.

• If you're using Podscribe for attribution, generate an API key in Podscribe and share it with Paramark on Slack. If you're using a vendor pixel or conversion mapping as part of the setup, confirm the event names and tracking approach with your Growth Advisor before launch.

• When available, also share a daily export with date, campaign or show name, platform, impressions or downloads, spend, and geography or test cell. This helps Paramark evaluate native lift readouts alongside attribution tracking and MMM.

Out-of-Home (OOH)

• Request a campaign delivery report from your OOH vendor or agency. Required fields: date, campaign or placement name, impressions or exposure estimates, spend, geography (US state or DMA preferred).

• If your OOH partner prefers not to send CSV files back and forth, a shared Google Sheet is acceptable. Paramark can work from a sheet where the partner enters daily spend and daily impressions or exposures directly.

• If the vendor provides spend and exposure in separate tabs or separate files, that is acceptable as long as the date coverage and geography are clear and the naming stays consistent.

• If the campaign is split across multiple markets or waves, keep the geography breakout in the file and note whether the data is by state, DMA, city, or another market unit.

• Upload to your Paramark Google Drive folder or share the working Google Sheet with your Paramark contact on the cadence agreed with your Growth Advisor.

Influencer

• Request a weekly or monthly performance export from your influencer agency or platform (e.g., Grin, IZEA, Creator.co). Required fields: date, creator or campaign name, impressions, spend.

• If your agency doesn't provide daily granularity, weekly is acceptable.

• If you're exporting influencer performance from Sprout Social, a combined Instagram/TikTok file is acceptable as long as it includes post date, creator/profile name or handle, platform (if mixed), and a delivery metric such as views or impressions. If Sprout does not include spend, share a separate spend file by creator and date so Paramark can join the delivery data to spend.

• Upload the files to your Paramark Google Drive folder and keep the column names consistent across recurring uploads.

CTV / Streaming (beyond MNTN — e.g., Samsung Ads, Hulu, Roku, Paramount+, Disney+)

• For CTV platforms not accessed via API, request a campaign delivery report from your account manager or DSP. Required fields: date, campaign name, impressions, spend.

• State-level geographic breakout is preferred where the platform supports it.

• Upload to your Paramark Google Drive folder.

National / Linear TV Post-logs

• If your TV data is delivered as a recurring post-log from an agency or vendor, a spreadsheet handoff is acceptable. A weekly delivery cadence with a one-week lag is fine when that matches the vendor’s reporting process.

• Please include the clearest time field available for each row, such as air date, week, flight window, or reporting week, plus spend and the core delivery fields your team tracks.

• When available, also include network, station, program, placement, market / geography, impressions or other delivery metric, and any campaign or vendor identifiers your team uses to keep recurring files consistent.

• If the report uses abbreviated or vendor-specific column names, please share a glossary or definition sheet for the report columns alongside the post-log so Paramark can interpret the file correctly without guesswork.

• Keep the column names stable across each recurring delivery when possible, and note clearly if a newer weekly file replaces prior numbers or only appends the latest reporting period.

• If your agency sends separate files for linear / national TV and scatter, that is acceptable. Label each file clearly by covered week and channel type, and keep the core fields aligned as much as possible so Paramark can reconcile the recurring handoff without manual guesswork.

Want to learn more about sharing your data? Check out other Paramark data sharing articles here