Sharing Actions between Apps

Shared Content and Updates

Any number of Apps can share one or more Actions.

In the above example of a company business card, the first 3 actions are unique to each employee app, while the following 5 Actions relate to the company and are common to all employee apps. Thus an update to the lead form will update all employee apps.

Discrete Behavior

Even though there is only one copy of a shared Action in an account, there are differences in how that Action behaves in each individual app.

• Shared Actions inherit the color theme and font of the host app so they might look different in different apps.
• Engagement metrics are tracked independently for each instance of an Action.
• Form Actions will automaticallly identify the source app, so the same Action can be used in multiple apps while still tracking the originating source.
• An option of the "IQ" feature will cause a query variable identifying the source app to be appended to all links originating from Link Action in the app. 

The Mechanics of Adding a Shared Action

All Actions created in an account are automatically added to the account's Library. One adds an Action that already exists in another app by using the "Add From Library" option and then searching for the target Action by name or tag.

When creating a new App from an existing App, the "Clone" feature allows one to designate which Actions will be shared.

One can also create App with shared Actions via API. A use case would be connected packaging where every product has a unique QR code/URL and where every corresponding product app shares all same Actions for simplified updates. This use case will benefit from discrete metrics and identified support forms. This application also leaves open the option to add a unique promotional action to a handful of product units as a prize to incentivise engagement.