Meta Ads Integration

In adstage, you can collect cost data from advertising campaigns running on Meta Ads (Facebook and Instagram), and integrate the Conversions API (CAPI) to send the conversion events collected by adstage back to Meta. The Meta Ads integration consists of three tabs: 채널 연동, 비용 연동, and 전환 API.

1. Integration Overview

Configure the following items in the adstage dashboard at Integration > Ad Channel Integration > Meta Ads.

2. Setting Up Cost Integration

When you connect a Meta ad account in the 비용 연동 tab, you can view the cost data of campaigns running on Meta Ads in the adstage dashboard.

Integrating with a Meta Account

Use Meta Business login (OAuth) for secure authentication.

1. In the 비용 연동 tab, enable the 비용 데이터 수집 switch.

2. Click the 연동 계정 추가 button. The Facebook Business login window opens in a new window.

3. Log in with your Meta account and approve the permissions so that adstage can access your ad data.

Integration Prerequisites

To proceed with cost integration, you need access to the Meta Business Manager and administrator permissions for the relevant ad account.

Selecting an Ad Account

Once authentication is complete, a list of ad accounts accessible with that Meta account is displayed.

1. Select one or more ad accounts to integrate. The account name, Ad Account ID, and Business Manager information are displayed, so verify that you have selected the correct account.

2. You can search the list by account name or ID, and you can also select all at once with 전체 선택.

3. After confirming the number of selected accounts, finalize the integration to connect those ad accounts with adstage.

Please Note

Ad accounts that are already registered are excluded from the integration. If all selected accounts are already registered, the integration will not proceed.

Managing Integrated Accounts

You can review integrated ad accounts in the account list of the 비용 연동 tab with the following information.

To disconnect an integration, click the delete button for the relevant account in the account list, then select 삭제 in the confirmation message.

Please Note

Deleting an account stops data collection for that account. Previously collected historical data is retained in adstage, but no new data will be collected.

Data Collected

Cost data is collected as follows.

3. Setting Up Conversions API (CAPI) Integration

When you integrate the Meta Conversions API (CAPI) in the 전환 API tab, adstage can send the events it collects to Meta from the server side without installing the Facebook SDK in your app. Even in iOS ATT environments, server-side transmission can improve attribution accuracy.

Entering the Pixel ID

Check the Pixel ID in Meta Events Manager, then enter it.

• Where to find it: Events Manager → Data Sources → Select Pixel → Settings → Pixel ID

Entering the Access Token

Generate an access token for the Conversions API in Events Manager, then enter it.

• Where to generate it: Events Manager → Data Sources → Select Pixel → Settings → Conversions API → Generate Access Token

The Access Token Is Stored Encrypted

The saved access token is encrypted and stored securely, and it is not displayed again after being saved. To change it, enter a new token again.

Test Event Code (Optional)

To validate events without affecting your production reports, set up a test event code. When switching to production mode, clear the code and save again.

• Where to find it: Events Manager → Test Events tab → Check the test code

Connection Test and Event Forwarding Settings

Once you save the Pixel ID and access token, you can use the following features.

Only events that have actually been collected appear in the event forwarding settings. If no events have been collected yet, they will appear in the list once data arrives from the app.

How CAPI Works

• User emails and phone numbers are hashed with SHA256 before being sent to Meta.
• event_id-based deduplication is automatically applied to prevent double counting with the browser pixel.
• Server-side event transmission bypasses iOS ATT restrictions to improve attribution accuracy.

4. Setting Up Channel Integration

In the 채널 연동 tab, register the information required to decrypt the Android Facebook Install Referrer.

Checking the Facebook App ID

Register your app in Meta for Developers, then check the App ID and enter it.

• Where to find it: Dashboard → Select App → Settings → Basic → App ID

Entering the Decryption Key

Enter the 32-byte decryption key (64 HEX characters) issued by Meta.

• Where to find it: Dashboard → Select App → Settings → Advanced → Install Referrer Decryption Key

The Decryption Key Is Stored Encrypted

The saved decryption key is encrypted and stored securely, and it is not displayed again after being saved. To change it, enter a new key again.

5. Precautions

Please note the following.

• Discrepancies in figures may occur between Meta Ads and adstage. This is due to differences in aggregation timing, time zones, and filtering criteria.
• If you revoke the permissions of your Meta account or the token expires, data collection may stop.
• If you change a campaign name in the ad channel, it may take time for the change to be reflected in adstage.
• To enable the Conversions API, both the Pixel ID and the access token must be saved.