MOBON Integration

Beta

The MOBON integration is still being verified with live advertiser accounts (the integration card shows a Beta badge). If the numbers in adstage differ from your MOBON reports, please let the adstage support team know.

In adstage, you can automatically collect spend, impressions, and clicks from MOBON (Enliple) campaigns and compare them with other channels in a single report. The integration is set up in the Cost Integration tab under Integrations > Ad Channel Integration > MOBON, and it uses your MOBON advertiser (or agency) login instead of a separate API key.

1. Integration Overview

Feature	Availability	Description
Cost collection	Supported	Spend, impressions, and clicks per campaign, collected automatically every 4 hours
Tracking link template	Not available	MOBON does not publish click macros. You can still report traffic under the `mobon.ads` channel with a custom deep link
Conversion sending	Not supported	MOBON does not publish an app postback specification for measurement partners
Channel name	`mobon.ads`	Shown as `MOBON` in report channel filters

2. Before You Start

MOBON does not issue a dedicated API key. You enter the same credentials you use to sign in to MOBON.

Field	Description
Account Label	A name to identify this account in adstage (for example `MOBON - Brand A`)
Login ID	Your MOBON advertiser or agency login ID
Password	The password for that account

The How to get your MOBON key box in the dashboard says the same thing: MOBON uses your existing advertiser (or agency) login ID and password, and no separate key is issued.

Please note — source IP registration

The MOBON API automatically allow-lists the IP address that makes the first call and blocks every other IP. Additional servers or IPs must be registered with MOBON separately.

For this reason, add the account only from the adstage dashboard. If you first test the API with the same ID from another server or PC, that IP gets registered and collection from adstage may be blocked. If that happens, ask MOBON to also allow-list the adstage server IP.

3. Connecting Your Account

Open the Cost Integration tab under Integrations > Ad Channel Integration > MOBON.
Turn on the MOBON Cost Integration switch, then click Add Integration Account. The button is disabled while the switch is off.
In the Integration Information Registration dialog, enter the Account Label, Login ID, and Password.
Click Integrate. Before saving, adstage calls MOBON with the credentials to confirm reporting access. On success you see "MOBON account has been successfully added." The password is stored encrypted.
The first collection starts right away. Once the account Status changes from Preparing to Success, the cost data is available in reports. This usually takes a few minutes.

If something is wrong with the input, you will see one of these messages.

Message	Cause
The key was rejected by MOBON. Please check the key and its permissions.	Wrong login ID or password, or the source IP is not on the MOBON allow-list
Could not reach MOBON to verify the key. Please try again later.	A temporary MOBON outage or the rate limit (120 calls per minute). Try again shortly
This account is already registered	The same login ID is already connected in this organization

If you have several advertiser accounts, add one account per login ID.

4. Managing Connected Accounts

Connected accounts are listed in the Cost Integration tab.

Column	Description
Account Name	The label you entered when adding the account
Status	Preparing (first collection running), Success (MOBON API working), Failed (data could not be fetched). Hover over Failed for a summary of the cause
Last Data Update	When cost data was last saved
Management	Delete icon. Confirm in the Delete Account dialog to disconnect

Good to know

Even in the Failed state, adstage retries on the next run and returns to Success once the cause is resolved. Authentication problems (password change, revoked access, blocked IP) must be fixed by a person.

Even in the Success state, no data arrives if no ads are running. If no cost data is saved for more than 3 days, a warning appears next to the status with the message "No ad cost data has been collected for N days."

Credentials cannot be edited. If you change your MOBON password, delete the account and add it again.

Turning off the MOBON Cost Integration switch stops collection for every MOBON account in this organization. The accounts remain, so collection resumes when you turn it back on.

5. Collected Data

Item	Description
Collection interval	Every 4 hours (01:00, 05:00, 09:00, 13:00, 17:00, 21:00 KST)
Update range	Last 30 days (D-30 to D-1, excluding the day of the update). The full range is re-fetched each time so later restatements are picked up
First collection	Starts right after the account is added and usually finishes within a few minutes. Same-day data is not collected, so today's numbers appear tomorrow
Data level	Campaign level (date x campaign). Ad group and creative data are not collected
Report metrics	Ad Spend (Channel), Impressions (Channel), Clicks (Channel)
Currency	MOBON does not document the reporting currency, so values are read as KRW (a Korean channel) and converted into your organization's base currency
Timezone	MOBON does not document the reporting timezone, so data is recorded as KST (Asia/Seoul). The dashboard also shows `Report timezone: KST`
Channel name	`mobon.ads`

Metrics reported by the channel itself are suffixed with (Channel) in reports.

Report metric	MOBON value
Ad Spend (Channel)	Spend (`advrtsAmt`)
Impressions (Channel)	Impressions (`viewCnt`)
Clicks (Channel)	Clicks (`clickCnt`)
Conversions (Channel)	Empty. MOBON conversions (`convCnt`) are shopping conversions, not app installs, so they are kept in the raw data only
Conversion Value (Channel)	Empty. MOBON total sales (`totalSales`) are also kept in the raw data only. Use revenue measured by the adstage SDK instead

Good to know

Campaigns are keyed by the MOBON campaign number (kpiNo), and the campaign name (kpiNm) is shown in reports.

Days where spend, impressions, and clicks are all zero are not stored.

6. Tracking Links and Conversion Sending

MOBON does not publish click ID macros or an app postback (conversion sending) specification. That is why MOBON does not appear in the ad channel list under Deep Links > Create or among the network presets for network postbacks.

What works today: create a Custom deep link and set the channel to mobon, 모비온, or enliple. Traffic from that link is reported under mobon.ads, the same channel as the cost data.
What to request: after cost integration is done, ask your MOBON account manager for the click ID macro and the conversion postback specification. Once you have the call URL and parameters, enter them in the URL template of Network Postback for the link. If the setup is unclear, send the specification to the adstage support team.

7. Cautions

Please note the following.

Numbers may differ between MOBON reports and adstage because of differences in aggregation timing, currency, and timezone.
Same-day data is not collected. Reports show data up to yesterday only.
Changing the MOBON password or losing account access stops collection and sets the status to Failed.
The MOBON API is limited to 120 calls per minute. adstage spreads its calls one day at a time, but calling the same account from another tool at the same time can hit the limit.
adstage only reads MOBON reports; it never changes campaign settings.

8. Troubleshooting

The account cannot be added

Check the login: confirm the ID and password work when signing in to MOBON directly.
Check IP registration: if the same ID was used to call the API from another server or PC, ask MOBON to also allow-list the adstage server IP.
Check the switch: Add Integration Account is enabled only while the MOBON Cost Integration switch is on.
Check for duplicates: make sure the same login ID is not already in the account list.

No data is collected

Check that the integration is on: confirm the MOBON Cost Integration switch is enabled.
Check that ads ran: confirm there was actual spend in MOBON for the period (days with zero spend, impressions, and clicks are not stored).
Check the range: same-day data is not collected, and only the last 30 days from the time of connection are fetched.
Check for a warning: look for the warning icon next to the account status.

Numbers differ from MOBON reports

Period: compare the same dates in KST.
Currency: adstage values are converted into your organization's base currency.
Granularity: adstage stores campaign totals only, so do not compare them directly with MOBON views split by ad group, creative, or web and mobile.

Contact the adstage support team if you need more help.

9. FAQ

Do I need to issue a separate API key?

No. MOBON authenticates with the advertiser (or agency) login ID and password. adstage obtains the access token internally, so there is no key issuance step.

Can I connect with an agency account?

Yes. The MOBON statistics API supports both advertiser and agency IDs. Only the campaigns visible to that account are collected.

Why are Conversions (Channel) and Conversion Value (Channel) empty?

This is intentional. MOBON conversions are shopping conversions, so they are not counted as installs or conversions. Measure performance with Ad Spend (Channel), Impressions (Channel), Clicks (Channel), and the event metrics adstage measures directly.

Does adstage backfill historical data?

It fetches up to the last 30 days from the time of connection. Anything older is not collected.

10. Reference Documents

MOBON API documentation — the API adstage uses for cost collection. It documents token issuance (POST /api/token), campaign statistics for advertisers and agencies (POST /api/report/ad/stats), the automatic allow-listing of the first calling IP with separate registration for additional IPs, and the 120 calls per minute limit.
MOBON API Center — redirects to the documentation above.
MOBON advertiser sign-in — where the login ID and password you enter in adstage are used.

MOBON Integration

Table of Contents