Aura from Unity

Overview

Aura from Unity connects OEMs and carriers with mobile advertisers to create value for users right out of the box.

Partner Capabilities

Capability	Details
Company Type	Ad Network
Deep Linking	Supported
Attribution	Click-Through Attribution View-Through Attribution
Ad Campaign Types	Acquisition campaigns
Ad Formats	Contact support at Aura from Unity for more information.
Click Types	Client-side click Server-side click
Supported Platforms	Android
Link Wrapping	Not Supported
Cost Ingestion Support	Supported
Cost Ingestion Types	via API (Beta) via Branch Ad Link
Cost Time Zone	GMT
Cost Data Scheduling	[ 4, 9, 12, 18, 24, 36, 48, 72, 96, 120, 240, 360, 480, 720 ] in hours from midnight
Cost Ingestion Types	Click/impression tracking link API
Pricing Models	CPI CPC CPA

Prerequisites

In order to enable Aura from Unity, you need to have completed the following:

Created a Branch Dashboard.
Have Branch's Performance product enabled for your Branch Account.
Implemented the Branch SDK into your mobile app (iOS | Android)
- Track events
Running campaigns through Aura from Unity.

Enable Aura from Unity

1. Enable Aura from Unity in Branch

In the Branch Dashboard under Ads > Partner Management, find/search for Aura from Unity. If you're already logged into the Branch Dashboard, you can also click here to go there directly.

Unity & ironSource
Even though Unity and ironSource have merged, Aura attribution configuration still falls under ironSource Aura in the Branch Dashboard.

Click the Save & Enable button.

2. Configure postbacks

Enabling Aura from Unity will automatically enable the following postbacks:

INSTALL
PURCHASE
OPEN
ACHIEVE_LEVEL
COMPLETE_TUTORIAL
COMPLETE_REGISTRATION
ADD_TO_CART
SHARE

You can configure these postbacks or add more under the Postback Config tab.

Send All Events

Optionally, you can check the checkbox for a given postback for sending all events. When checked, all events will be sent regardless of attribution. Otherwise, the postback will only fire for events attributed to Aura.

For more in-depth postback configurations, view our guides:

3. Configure Attribution Windows

After configuring your events, navigate to the Attribution Windows tab to set windows by attribution type.

Recommended Attribution Windows

Attribution Type	Window
click to session start	90 days
click to install	30 days
click to conversion event	90 days
impression to session start	1 day
impression to install	1 day
impression to conversion event.	1 day

4. Set up Cost Data

Beta for Non-SANs
Cost Data for Non-Self-Attributing Networks (Non-SANs) is a feature currently in Beta; be aware that there may be unexpected bugs/behaviors until the full release.

To set up cost ingestion for Aura from Unity, you will need to authenticate using your Authentication Token. Please reach out to your Aura from Unity account manager if you have trouble finding these values.

Enter your Authentication Token, and click Save Authentication

5. Create Branch Ad Link

Next, you'll need to create a Branch Ad Link for your Aura from Unity campaigns in order for Branch to properly attribute conversions.

help.branch.io

Create Ad Links

The Branch Ad Link you create will be placed in your Aura from Unity campaign.

6. Verify Data in Branch

After launching your Aura campaigns, and conversions begin to happen, you'll want to verify data is being sent from Branch to Aura. You can look at the Branch Dashboard's Liveview Webhook Records and apply the following filter:

Filter	Operator	Value
ad partner (3p)	equals	`a_aura`

Once applied, data should flow through the Liveview, and you can see the data being sent to Aura from Unity from Branch.

Verifying Cost Data

To verify that cost data is flowing into Branch, you need to have the following:

Completed all implementation steps above
You need to already be live with campaigns running for the ad network
Wait 24 hours for data to be pulled in