Create inmobi-cohort.md #96
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports MegaLinter is graciously provided by |
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
There was a problem hiding this comment.
Thanks for drafting this Brandon!
Overall LGTM, let us hold off till we work with InMobi for the test sync (and get their confirmation the setup/format looks good).
Also there are some warning from GitHub Actions about word choices -- I think those are checks/best practices applied from tech writter, so can be addressed them before we release :)
| 1. In Amplitude Data, click **Catalog** and select the **Destinations** tab. | ||
| 2. In the Cohort section, click **Amazon S3 (Cohorts)**. Don't select **Amazon S3** for this integration. | ||
| 3. Paste in the details you've obtained from the InMobi team under **Bucket Name**, and **Bucket region**. | ||
| 4. Enter your **Bucket Path** (which should be your advertiser_id), and enter a **Name** for the destination. The name is used when syncing a cohort from Amplitude. |
There was a problem hiding this comment.
For **Bucket Path** (which should be your advertiser_id), let us hold on this draft until we work with InMobi people to confirm this.
| 4. (Optional). Set the following two optional parameters: | ||
| - **Routing Key:** Enter a string to be appended to the end of the cohort file name in S3. We recommend using your advertiser_id. |
There was a problem hiding this comment.
See my comment above, regarding how we pass advertiser_id we can work with InMobi to finalize the format works, then we can update doc.
Changed some of the language to be more active voice
Amplitude Developer Docs PR
Description
Describe your changes.
Deadline
When do these changes need to be live on the site?
Change type
PR checklist:
mkdocs serve.mkdocs servedidn't generate any failures.@amplitude-dev-docs