-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Moloco MCM destination beta doc #6399
Conversation
…y destination code (old name moloco-rmp).
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
src/connections/destinations/catalog/moloco-rmp/images/mcm-destination-monitoring.png
Outdated
Show resolved
Hide resolved
src/connections/destinations/catalog/moloco-rmp/images/mcm-mappings.png
Outdated
Show resolved
Hide resolved
src/connections/destinations/catalog/moloco-rmp/images/page-identifier-token-example.png
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for finding alternatives to your screenshots!
If you have any questions or comments about my review, please feel free to tag me in a comment!
|
||
In the mappings tab, some fields are chosen by default if some common fields map to Moloco Event’s fields. If the mapped key does not exist in the input data, it won’t trigger an error and will just not pass any value. | ||
|
||
If you are using **the default fields in a custom way**, please confirm that your mapping meets Moloco's requirements. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might need more context on this: what would using the default fields in a custom way look like? Where could a user read more about Moloco's requirements?
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
Once a user is identified, each call to Segment's [Track method](/docs/connections/spec/track/) automatically records the user ID. | ||
Users that are not logged in can be tracked using an [anonymousID](/docs/connections/spec/identify/#anonymous-id). Moloco Commerce Media does not use anonymousIDs for users that are not logged in. Segment recommends formatting your anonymousID in UUID format. | ||
|
||
> info" " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> info" " | |
> info " " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm! after it gets approval from @tcgilbert we'll be good to go.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two things:
- add the requested snippet (this will autopopulate details about each action and it's field in your docs
- you need to rename the folder name from
moloco-rmp
toactions-moloco-rmp
as the slug of your integration is used to autogenerate links out to your docs from other parts of our application
Co-authored-by: Thomas Gilbert <64277654+tcgilbert@users.noreply.github.com>
Done! |
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Hi team, I could find the doc to this URL (https://segment.com/docs/connections/destinations/catalog/actions-moloco-rmp/) but it is not indexed and listed in https://segment.com/docs/connections/destinations/catalog |
Hi @samir-moloco: the @tcgilbert - is there a way to tell which categories this destination will populate into? I can't see anything in PAPI! |
@samir-moloco can you send me your email address? Essentially, the last step you need to complete to get your destination live is to add the integrations catalog metadata in our developer portal. This is where you will select categories, add logos, etc. Once done, and your integration is in public beta, the docs will populate correctly. |
@tcgilbert my email address is samirh@moloco.com |
@samir-moloco I just sent a developer portal invitation to your email address, as well as heonjang.lee@moloco.com. Once accepted, you should be able to access the developer portal here: https://app.segment.com/dev-portal/overview. Please ensure you're logged into a Segment account associated with the same email address to which the invitation was sent (You may have to create your segment account). In case you use a Segment account tied to a different email address, just let me know, and I'll send an invitation to the correct address. |
Thanks got the invite but I noticed I previously used samir.hammoudi@moloco.com for my Segment account so would appreciate if you resend an invite to this email address instead, thank you!! |
Hi @tcgilbert we did all the required steps on the developer portal and submitted for review to move to public beta. Hopefully this get approved soon. Thanks again for your review on this doc! |
hey @samir-moloco - great! looks like we have everything needed on our end to move your destiantion into public beta. Have you completed testing the Integration, and are confident it behaves as expected? If so, I'll go ahead and make the destination live. Also just sent another dev portal invite to samir.hammoudi@moloco.com |
Hi @tcgilbert excellent! yes I have tested the integration and it works great! thanks in advance to making it public beta!! |
I have gone ahead and made your integration live. Twilio Segment is excited to move your new integration into the Public Catalog! The mappings on your docs page will populate once our docs site rebuilds on Tuesday. To move out of beta, you can write back into partner-support@segment.com once you have at least one customer using the integration, and you are confident that the beta status is no longer applicable. If you have any questions or concerns, please let me know |
@tcgilbert Thank you for promoting our destination to Public Beta! I go under https://segment.com/docs/connections/destinations/catalog/#advertising and click on the Moloco MCM destination. I get a 404 instead of getting to https://segment.com/docs/connections/destinations/catalog/actions-moloco-rmp/ Let me know if we miss some configuration or if we should wait for something to rebuild on your side. Thanks! |
hey @samir-moloco - thanks for flagging! I just put in a patch for this. This will be fixed when the site rebuilds tomorrow afternoon. If there is anything else I can assist with let me know |
Confirmed it's now fixed, thank you @tcgilbert ! |
Proposed changes
Adds the documentation for our platform's Segment Destination (Moloco MCM).
Merge timing