# Sending Media Source Data

Send media data of where you acquired the users to our system, we will use this in our systems to be able to segment the user base and proved media source specific rewards. 

{% hint style="info" %}
This is related to intialization of the SDK. 
{% endhint %}

{% hint style="warning" %}
**Other than mediaSourceName which is mandatory, others are optional.** However, it is highly recommended to provide us all these data for us to tailor the rewards journey towards different media sources. 
{% endhint %}

<table><thead><tr><th width="223">Paramater</th><th width="120">Data Type</th><th>Description</th></tr></thead><tbody><tr><td>mediaSourceName [<strong>Mandatory]</strong></td><td>string</td><td>Can be used to send the source name of where you got the user </td></tr><tr><td>mediaCampaignName</td><td>string</td><td>Can be used to send the campaign name of where you got the user</td></tr><tr><td>mediaSourceId</td><td>string</td><td>Can be used to send the source id of where you got the user</td></tr><tr><td>mediaSubSourceId</td><td>string</td><td>Can be used to send the Sub Source id of where you got the user</td></tr><tr><td>Incentivized</td><td>boolean</td><td>Can be used to send if the user acquisition was done via incent channels or non incent channels.</td></tr><tr><td>mediaAdsetName</td><td>string</td><td>Can be used to send the adset name of where you got the user</td></tr><tr><td>mediaAdsetId</td><td>string</td><td>Can be used to send the adset id of where you got the user</td></tr><tr><td>mediaCreativeName</td><td>string</td><td>Can be used to send the CreativeName of where you got the user</td></tr><tr><td>mediaCreativeId</td><td>string</td><td>Can be used to send the creativeId of where you got the user</td></tr><tr><td>sub1</td><td>string</td><td>Can use this to to store any type of data. <br><br>Currently only used to store data can't be received on the postback</td></tr><tr><td>sub2</td><td>string</td><td>Can use this to to store any type of data. <br><br>Currently only used to store data can't be received on the postback</td></tr><tr><td>sub3</td><td>string</td><td>Can use this to store any type of data. And can be sent back on the postback as well.<br><br><a data-mention href="/pages/wA6KNwNFL96U0Tpn5ZNv">/pages/wA6KNwNFL96U0Tpn5ZNv</a></td></tr><tr><td>sub4</td><td>string</td><td>Can use this to store any type of data. And can be sent back on the postback as well.<br><br><a data-mention href="/pages/wA6KNwNFL96U0Tpn5ZNv">/pages/wA6KNwNFL96U0Tpn5ZNv</a></td></tr><tr><td>sub5</td><td>string</td><td>Can use this to to store any type of data. <br><br>Currently only used to store data can't be received on the postback</td></tr></tbody></table>


---

# Agent Instructions: 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://sdk-doc.tyrads.com/v3.0/getting-started/advanced-options/sending-media-source-data.md?ask=<question>
```

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.