> For the complete documentation index, see [llms.txt](https://help.rzr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rzr.com/readme/mmp-integration-guide/singular-integration.md).
# Singular Integration
### Step 1: Integrate RZR as a partner
To add **RZR** as a partner in your **Singular dashboard**, follow these steps:
1. Go to your **Singular** dashboard.
2. Click **ATTRIBUTION** > **Partner Configuration**.
3. Select **Add a Partner**.
4. Choose **RZR** from the list.
### Step 2: Setting up an App/site
To add the **app and site (app version)** for your campaign, follow these steps:
1. On the **Partner Configuration** page, click **+Add App Site**.
2. In the **App** drop-down, select the **app** you want to run the campaign for.
3. In the **Site** drop-down, select the **latest version** of the app.
4. Mark the **Include View-Through Attributions** box if it is not already selected. This option enables the attribution of impressions.
5. Mark the **Enable Fraud Postbacks** box if it is not selected by default.
6. Mark the **Send Postbacks to RZR on All Installs** box. This option helps optimize RZR's machine-learning models for precise targeting by sharing unattributed data.
7. Keep the **Click-Through Attribution Lookback Window** at the default value (**7 days**). This is an industry-standard value, and changing it may result in inaccurate reporting.
For re-engagement, please ensure the re-engagement inactivity window is defined the default value is of 7 days.
8. In the **Send In-App Events to RZR** drop-down, select **On**. This option enables the attribution of all events that occur throughout the campaign.
### Step 3: Configure Postbacks
1. For In-App Postback Events, select the **starting point** and set up the **postback window duration.**
2. If the client sets the conversion flag to 0 during the in-app postback event setup, both RZR-attributed (install claim) and non-attributed events can be included in the postbacks for that specific event.
**Note:**
* Setting **Conversion Flag = 1** indicates that only RZR attributed Postbacks will be sent.
* To receive **all events (including non-attributed ones)**, the **“Send All”** option needs to be enabled. In that case, even events with **Conversion Flag = 0** would be sent via postbacks when “Send All” is enabled.
**Note:** To avoid discrepancies in ad revenue data, please ensure that the **{RAW\_AMOUNT}** macro is passed in the **purchase\_revenue parameter** of the postback URL, instead of **{AMOUNT}**. This helps prevent values less than 0 from being rounded off to 0, which can lead to inaccurate reporting.
To validate this, the client can navigate to the In-App Event Postbacks section and select the highlighted option (as shown in the screenshot) to view the configured postback URL.
### Step 4: Cost Integration
For RZR, we have a data connection with Singular, which enables us to share cost data using an S3 bucket.
For more details on the fields shared, please refer to the link below:\
[Singular RZR Data Connector](https://support.singular.net/hc/en-us/articles/360041181092-Aarki-Data-Connector)
**Note**: If cost data is missing, please be aware that Singular retrieves data daily for the last seven days. If the issue date falls within this seven-day timeframe, the data issue should be resolved automatically.
### Step 5: Audience Integration
1. Navigate to **Audiences** > **Distributions**: This section lists all available audience partners for distribution.
2. Click on the Desired Ad Network: Select the ad network (e.g., RZR) where you want to distribute your audience segment.
3. Enter the **Provided Token**: In the Network Configuration dialog that appears, input the token in the designated field.
4. Configure Segment Settings: Under the Segment Configuration section, you'll see a list of your audience segments.
5. Enable the Segment: Toggle the switch to enable the segment you wish to distribute.
6. Save the Configuration: After configuring the necessary settings, click Save to finalize the distribution setup
***
Conversion flag difference b/w 0 and 1 and send all : Ensure for each event the conversion flag is set to 0 and not 1.
Define the process to add the s3 bucket folder on singular UI
Once your partner is ready to deliver reports via s3, you will need to setup a Data Connector in Singular to enable data processing.
* Go to Settings > Data Connectors in your Singular account.
* Click Add a New Data Connector and enter the partner's name.
* In the New Connector window, fill in the Folder Name--this should match the folder your partner created within the s3 bucket to deliver your reports. (Ask RZR account manager to provide the folder name)
* Click Save.
***
This document outlines the complete setup details required to configure your Singular account. Please review each section carefully and follow the outlined steps to ensure accurate tracking, attribution, and reporting.
If you need any help with the configuration document, feel free to reach out to your **RZR Account Manager/Account Coordinator** for assistance.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://help.rzr.com/readme/mmp-integration-guide/singular-integration.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.