Skip to main content
Act-On Software

Sharing Content - How it works

 

Act-On’s Content Sharing feature allows marketing agencies to share marketing assets with managed accounts. This article provides the basics on how to share assets.

Account managers are able to share content (forms, email templates, and automated program templates only at this time) with any managed account. To do this, an account manager needs to:

  1. Set up sharing privileges
    1. The account manager selects Share in the list view of managed accounts.
    2. In the dialog, the account manager checks Can Share and/or Can Subscribe.
      • Can Subscribe means that the managed account can receive assets from any other account in the group.
      • Can Share means that the managed account can share an asset with any other account in the group.
  2. Share an asset
    1. The account manager navigates to the preview of the asset they want to share and selects Share. (The account manager needs to be in the appropriate account and previewing the appropriate asset to share.)
    2. In the dialog window with the list of accounts that can receive the asset that displays, the account manager needs to select the accounts to share the asset.
  3. Accept the asset from the shared account
    1. The account manager navigates to the Inbox that displays in the Home drop-down menu.
    2. The user can preview the asset, accept it, or decline it.
    3. Once the asset is accepted, it appears in the Default folder of the asset type. For example, an accepted form will appear in the Form default folder.

Please note that our platform does not currently support the sharing of assets from a managed account to the main account.

Forms

  • What can be shared from Parent to Child accounts in Lab Forms?
    • Forms
    • Templates
    • Content Fragments
    • All assets attached to a Form (images, documents, etc.)
  • What is not carried over from Parent accounts?
    • CRM settings
    • Form Submissions list (a new list is automatically created in the Child account)
    • Fragments within a shared Form
    • Landing Page URL (when the Form redirects to a Landing Page upon submission)
    • CAPTCHA domains
       
  • What happens when a form is shared from parent to child account?
    • Forms are shared when the Child account accepts, any changes that are made to a shared form prior to it being accepted will be reflected in the Child account (even after the Parent account has shared it).
    • Field mapping: A new (contact) list gets created in the child account based on mappings in the parent account (but without any data submissions from the Parent account).
      • This list can then be modified in the Child account
    • Landing Page Redirect: When a form that redirects to a Landing Page is shared, that Landing Page and any associated assets/fragments will be added to the Child account (and account ID's switched out to match those of the Child).
        • A new default URL is created in the Child Account when a Form that redirects to a Landing Page is shared from a Parent.
    • Fragments within a Form: Fragments within a shared form will be condensed into content and unavailable for re-use by the Child account.
      • If the shared form is set to redirect to a Fragment in the Parent account, that Fragment will be shared with the Child account.
      • Otherwise, if the Parent wants to share a Fragment they will need to do so separately.
    • CAPTCHA Domains: Will not be shared from the Parent account, the Child Account CNAME/Account ID will be automatically added to the CAPTCHA when a form is shared, which will allow the CAPTCHA to function on all pages associated with the CNAME/Account ID. Additional domains can be added by the Child account.
    • Response: All of the settings from the Response section of a Form from a Parent account will be retained when shared with a Child account, except CRM settings.

Landing pages

  • What can be shared from Parent to Child accounts in terms of landing pages?
    • Landing Pages
    • Landing Page Templates
    • Assets attached to a Landing Page (images, documents, etc.)
      • Attached assets supported up to 3 levels (e.g. Landing Page contains a Form which redirects to another Landing Page which contains an image)
  • What is not carried over from Parent accounts?
    • Redirect URL for Disabled page (Properties tab)
    • Signature from Parent account (Signature block will share but must be updated with Child account’s signature- can be done within the Signature block)
       
  • What happens when a Landing Page is shared from parent to child account?
    • Landing Pages will not reflect updates made in the Parent account after the asset has been shared, even if the Child has not yet accepted the asset (Forms will reflect changes up until being accepted by the Child)
    • URLs and IDs for any assets shared from a Parent account are updated in the Child account so that changes to the Parent asset don’t impact the Child (e.g. if an asset is deleted from the Parent account)
  • Was this article helpful?