Cross-promotion between two apps with an API call

[Adam_R_Fromson]

So, if I wanted to have the notification of a person who opts into a landing page on one app notify back to the app that sent emails initially referring their list to the landing page to begin with, how do I write that api call? Or can I? Would like to keep track on the original app who’s opting into the offers they are being presented, wasn’t sure of a best practice.

[TomScott]

I’m not sure I’m clear here, so forgive my confusion.

• Infusionsoft Application A has a campaign with a Landing Page Goal.
• Infusionsoft Application B has a broadcast with a link to Application A’s Landing Page Goal.

You want Application A to notify Application B? What kind of notification?

This kind of integration will generally require custom code on a third party server, in which case it would look like this:

• Infusionsoft Application A has a campaign with a Landing Page Goal leading to a Sequence containing a Web Request action.
• Infusionsoft Application B has a broadcast with a link to Application A’s Landing Page Goal.
• User submits form on Application A’s Landing Page.
• Application A achieves the Landing Page Goal and proceeds to trigger a Request to Custom Application C, living on a hosted server.
• Custom Application C receives the request and accesses Application B’s API to generate a new object representing the action.

Still, this seems very convoluted for something that is generally done just inside one Campaign in a single Infusionsoft Application. Maybe if you describe what you are trying to achieve as the end-goal we can find an easier way to go about it?

[Adam_R_Fromson]

I get the feeling I am wildly overcomplicating this.

What I’m trying to accomplish is to get a campaign started in one app, but
when someone goes to the recommended landing page, hosted by the second
app, their opt in should trigger the stopping of his email sequence.

I hope this clarfies, but let me know if you have questions.

Thanks,

[TomScott]

I passed this question along to our API Support Representative, and this was his reply:

@Jonathan Smith

Depending on how the email is written it could be against Acceptable Use.

To solve the issue they just need to create a custom field that is populated when the link is clicked in the email with the referring application name. That would put the referring application then they can get an update REST hook and check to see what the referring application is.

That being said the contact didn’t opt into receive marketing emails from the other company which means that explicating permissions to send emails wasn’t obtained. If they write their own email and have a small section of the email for saying you might also be interested in this then it would be alright. Sending an email devoted to other companies or other things that weren’t part of the explicit permissions obtained aren’t allowed though.