Setting Up Adjust and Google Play Console Before SDK Integration
Before integrating Adjust (for ad attribution) and Google Play Billing into a Flutter app, there’s dashboard-side setup to handle first. This is a record of configuring both Adjust and Google Play Console in parallel, before touching any SDK code.
Related articles (SDK integration):
- Flutter + Adjust SDK: How Ad Attribution Works and How to Implement It
- Flutter WebView + Google Play Billing Implementation Guide
Setting Up the App in the Adjust Dashboard
Registering a New App
Log into the Adjust dashboard (dash.adjust.com) and create a new app.
- “AppView” → “Add app”
- Enter the app name (using a placeholder name for testing)
- Select platform(s) (Android / iOS / both)
Getting the App Token
Once the app is created, an app token is issued — a 12-character alphanumeric string needed for SDK initialization.
App token: xxxxxxxxxxxx (12-character alphanumeric)This token gets used later in the Flutter code.
Basic Settings
Settings configured at app creation:
| Setting | Value | Notes |
|---|---|---|
| Reporting currency | JPY | Display revenue in Japanese yen |
| COPPA | Disabled | Not a children’s app |
| Outside European Economic Area | Enabled | Measure traffic from outside EEA |
COPPA (Children’s Online Privacy Protection Act): A US law protecting the online privacy of children under 13. Enable this if the app targets that age group.
EEA setting: Due to GDPR, collecting data from users in the European Economic Area requires consent. Enabling “Outside EEA” allows unrestricted data collection from users outside the EEA.
Platform Settings
After app creation, configure the package name for each platform (Android / iOS).
App settings → Platform → Android| Field | Value |
|---|---|
| Package name | com.example.yourapp (must match AndroidManifest.xml) |
| Google Play Store URL | Leave blank (not needed before publishing) |
This links Google Play Console to Adjust.
Creating Event Tokens (Optional)
If you need event tracking, create event tokens at this stage.
Settings → Events → Create new eventEvents created for this project:
| Event name | Unique | Purpose |
|---|---|---|
| Registration | ON | Member registration completed |
| Product purchase 1 | OFF | Billing (item 1) |
| Product purchase 2 | OFF | Billing (item 2) |
| Product purchase 3 | OFF | Billing (item 3) |
An event token is automatically generated after adding each event, and used on the SDK side.
Event Configuration Notes
Unique Events
Checking “Set as unique event” means the event is recorded only once per device.
| Event | Unique | Reason |
|---|---|---|
| Registration | ON | One action per user |
| Purchase | OFF | Can happen multiple times |
Even if the SDK sends duplicates, Adjust counts it as once — a safety net.
Event Rules
When creating an event, there are Status options for “Flow verification”, “Source verification”, and “Revenue verification”.
| Status | Meaning |
|---|---|
| Off | Rule disabled |
| Published | Active in production |
| Test | Validates without affecting reports |
| Paused | Temporarily disabled |
Each rule’s role:
| Rule | Function | Notes |
|---|---|---|
| Flow verification | Checks event sequence and conditions | Paid plan |
| Source verification | Validates sender (fraud prevention) | Available on free plan |
| Revenue verification | Validates amounts for revenue events | Paid plan |
Leave everything Off during testing. Confirm that event tracking works first, then enable what you need.
Google Play Console Developer Registration
Account Creation and Payment
A one-time $25 registration fee is required for a Google Play Console developer account.
- Go to Google Play Console
- Log in with a Google account
- Proceed to developer registration
- Pay the $25 fee
Identity Verification
Developer registration requires identity verification in two steps.
1. Identity Authentication (ID document)
One of the following:
- My Number Card ✅
- Driver’s license
- Passport
The My Number Card went through quickly.
2. Address Verification
This was the tricky part. Proof of address requires one of:
- Driver’s license
- Bank account statement
- Mobile carrier statement
- Utility bill
Problem: Nobody has paper statements anymore. Banks and carriers have moved everything online.
Solution: Downloading an online bank statement as a PDF from Shinsei Bank worked — the address was included. That got it through.
How Long Verification Takes
The UI says “1–3 business days,” but in practice it took about 12 hours.
Submit → ~12 hours later → Verification complete emailFaster than expected.
After Verification
Once verified, all Google Play Console features become available:
- Publishing apps
- Registering in-app products
- Setting up license testers
- Using Google Play Billing
Additional Auth on Android
After verification, install the Google Play Console app on an Android device, log in with the same account, and complete phone number verification.
Creating the App in Google Play Console
New App Creation
- Log into Google Play Console
- Click “Create app”
- Fill in the details:
| Field | Value |
|---|---|
| App name | Placeholder name for testing |
| Default language | Japanese |
| App or game | App |
| Free or paid | Free (fine for apps with in-app purchases) |
Internal Testing Setup
Use “Internal testing” for billing tests — no review required, supports up to 100 testers.
Testing & releases → Testing → Internal testing → Get started → Create new releaseUploading the AAB File
On the internal testing release screen, upload the App Bundle (AAB).
Building with Flutter:
flutter build appbundle --releaseGenerated file:
build/app/outputs/bundle/release/app-release.aabDrag and drop this into the “App Bundle” area.
Important: At least one AAB upload is required before in-app products can be registered.
Release Details
| Field | Value |
|---|---|
| Release name | Auto-filled (editable) |
| Release notes | Anything works for testing |
Upload Warnings
Some warnings may appear after uploading — these are fine to ignore for internal testing:
| Warning | Meaning | Action |
|---|---|---|
| No testers assigned | Add them later | After publishing |
| Debug symbols not uploaded | For crash analysis | Not needed for internal testing |
Click “Save and publish” regardless of warnings.
Post-Publish State
After publishing, the internal testing screen shows:
- Temporary app name:
com.example.app (unreviewed) - Status: Published to internal testers
- Unreviewed (internal testing skips review)
Adding Testers
Click the “Testers” tab on the internal testing page.
- Click “Create email list”
- Enter a list name (e.g.,
Testers) - Add the Google account email(s) to use for testing
- Save
Check the list and save — those accounts can now download the app. Copy the “Test link” to access it on a phone and download from Google Play.
Registering In-App Products
In-app products become available after uploading the AAB.
Setting Up a Payments Profile
First, set up a payments profile (payments account) via “Monetize with Google Play”:
| Field | Value |
|---|---|
| Business/Organization name | Your name if individual |
| Products or services sold | Computer software |
| Customer support email | Contact email |
| Name on credit card statements | Name shown on user’s billing statement |
Creating One-Time Products
Monetize with Google Play → Products → One-time products → Create one-time product| Field | Example | Notes |
|---|---|---|
| Purchase option ID | item001 | Start with a lowercase letter; underscores not allowed |
| Purchase type | Purchase | Leave as-is |
| Tags | (blank) | Optional |
Set the price via “Set prices” — e.g., ¥100 for testing.
Note: There’s no duplicate feature, so multiple items must be created one by one.
Items created for this project:
| Item ID | Name | Price |
|---|---|---|
item001 | Test item 1 | ¥100 |
item002 | Test item 2 | ¥500 |
item003 | Test item 3 | ¥1000 |
Adding License Testers
Register the Google account(s) that will make test purchases. Without this, test purchases will be charged for real.
Important: License testing is a global Google Play Console setting, not per-app.
← All apps (top left) → Back to home → Settings → License testingAdd the test Google accounts (the account logged in on the test phone) here, and purchases will no longer result in real charges.
Select the mailing list created for internal testing and save.
Dashboard Setup Complete
At this point, both Adjust and Google Play Console are fully configured on the dashboard side.
| Service | Completed Setup |
|---|---|
| Adjust | App created, event tokens issued, package name configured |
| Google Play Console | Internal test published, in-app products registered, license testers configured |
| Service | Work | Time Required |
|---|---|---|
| Adjust | App creation, token issuance, event setup | A few minutes |
| Google Play Console | Developer registration, identity verification | ~12 hours after submission |
| Google Play Console | App creation, internal testing, in-app products | ~30 minutes |
Adjust is ready immediately. Google Play Console takes time for identity verification, so submit that first.
If the address verification step is giving you trouble, try downloading a PDF bank statement — it often includes your address.
For SDK implementation, see the related articles: