For AI agents: the complete documentation index is available at https://docs.clickmax.io/en/llms.txt, the full documentation bundle is available at https://docs.clickmax.io/en/llms-full.txt, and this page is available as Markdown at https://docs.clickmax.io/en/guides/import-a-package-as-an-affiliate.md.
  • English

      • I received a package — how do I import it and start selling?

      A shared package brings a funnel, pages and a product into your account ready-made. You do not build anything — you adjust and publish.

      Before you start

      • Role: Owner, Admin or Editor.
      • You need a Clickmax account. If you do not have one yet, the import link itself offers to create one.

      Before importing, the link shows you the Package content. It is worth checking the package suits your audience before it takes up space in your account.

      2. Choose the project

      Pick a Destination project — an existing one, or a new one to receive the package. One project per package makes life much easier later on: see project or workspace.

      3. Connect a domain

      Choose a Domain you have already connected, or leave it for later. To sell on your own address, see publish with your own domain.

      If the package funnels have a quiz, calendar or webchat, the Choose your quiz, calendar and channel section lists those steps. For each one, pick a quiz, calendar or webchat of yours, or leave it on Set up later. If the producer included that quiz, calendar or webchat in the package, the step already arrives linked to your copy; otherwise it arrives pending and you choose it on the canvas. Only active quizzes are listed, and the calendar link uses the project chosen above.

      Any offers the producer did not share arrive marked Not shared, and you have to select one of your own offers for them. Where the offer was shared, keep Keep original offer (affiliate) so the sale is credited to you as an affiliate.

      A shared offer shows No affiliation when you cannot become an affiliate of its product. The reason appears right below it:

      • the producer turned off affiliation for the product;
      • the offer no longer exists;
      • the producer suspended your affiliation to that product.

      In these cases, select one of your own offers instead. The package does not import while any offer is still tied to the original, because the checkout would not credit your commission. If you want to sell the producer's offer, ask them to fix it and open the link again.

      4. Finish the import

      Click Start import. Once it finishes, the structure appears under My Funnels, ready to edit. You can close the window while it runs — you are notified when the import is complete, and the record stays in the Imported packages tab.

      Whenever an item in the package points to another item in the package, it arrives pointing to your copy: an automation that filters by a page of the package looks at the imported page, and a funnel trigger looks at the imported funnel. References to things that only exist in the producer's account (segments, broadcasts, capture links, Instagram posts) arrive empty: the step or trigger that used them does nothing until you pick your own equivalent.

      The items the producer sees under Also included (a quiz, a custom field…) are created in your account along with the content. If your account cannot create one of them, the whole import is refused with the reason, and nothing is created.

      Custom fields are matched by the field identifier. If you already have an active field with the same identifier and the same type, the package uses yours and leaves it (and its options) untouched. If the identifier matches but the type differs, or your field with that identifier is deactivated, the package creates a new field with a number appended to the identifier (for example, cpf_2). In that case, message variables such as {{custom.cpf}} keep reading your old field: switch them to the new identifier if you want the package field's value.

      A sales pipeline in the package arrives with its stages, rules and stage automations, and no opportunities. Attendant roles with the same name as one you already have use yours. The producer's attendants do not come along: each one becomes a row in the Connect to activate panel, and the attendant you pick joins the pipeline's rotation and routing criteria. Stage automations arrive turned off: review each one and turn it on in the stage itself. HTTP request credentials do not come along, and the Outbound webhook arrives without a URL; enter your own address before turning it on.

      An AI agent from the package arrives in My agents as a draft, already linked to the automations that use it. It uses your API key: if you have a single active key from the agent's provider (OpenAI or Anthropic), it is already selected. With no key, or more than one, the key becomes a row in the Connect to activate panel; you can also pick it in the agent's Configuration tab. Then review and publish the agent; until then, the steps that use it do not answer. In the Knowledge tab, link and FAQ sources show as pending: click sync on each one to send it to your provider account. Documents arrive with their name only; upload the file again.

      A quiz or form in the package arrives ready and already linked to the funnel, pages and automations. The tags and lists it applies use yours with the same name (or are created). Before promoting, check what belongs to your account: notification emails, Slack, the external webhook and your own domain arrive empty.

      The package's webchat channel becomes a new channel in your account, with the same appearance, welcome message and pre-chat, and the pages and the funnel's webchat node already point to it. It arrives on the default chat address, without the producer's own domain and without limits on which sites can show the widget. In the pre-chat, the step that handed the conversation to someone in the producer's account now leaves it in the queue, unassigned. The channel's Live Chat automations are not included: set up your own in the Automations tab.

      Service teams arrive with their name and distribution mode but no members, because the people on the team belong to the producer's account. Each of the producer's members becomes a row in the Connect to activate panel: the attendant you pick joins the team with the weight and rules that member had. Do this before turning on the automation that distributes to the team.

      A schedule from the package arrives in your account with no one attending and with its public link turned off. Pick who attends in the Connect to activate panel (the public link goes back to how the producer had it) or directly in the schedule. The funnel's schedule node already points to your copy. Reminders from the Notifications tab arrive turned off and without a tag; the producer's sender and WhatsApp template become rows in the Connect to activate panel. Complete each one and turn it on. If the schedule asked for a verification code by email or WhatsApp, verification arrives turned off until you pick the sender (in the panel or in the schedule) or the template (in the schedule).

      Some items arrive with adjustments:

      • Proposal templates arrive complete, with their pages and the current document. Proposals the producer already generated are not included.
      • Tracked links in messages become Clickmax short links in your account, with the same destination. If the producer used a custom domain for them, the link moves to the Clickmax domain.
      • Each automation's incoming webhook gets a new URL. An HTTP Request in the package that called the webhook of another automation in the package arrives calling your copy. If it called an automation that is not in the package, the URL arrives empty: enter your own webhook URL before activating it.
      • Studio templates live on the computer of whoever saved them and are not included. The Request creative from the Studio step needs one of your own templates.

      A webinar from the package arrives as a draft, with no sessions or registrants: review the scheduling and publish it when it is ready. If the producer used a video uploaded to Clickmax, upload your own. A members area arrives with a new subdomain, no students, and WhatsApp login turned off; connect your domain and number to it if you want. Automation filters that pointed to a specific session of the producer now match any session of the imported webinar.

      If the package has Max Design pages, the project also appears in Marketing → Max Design, with the producer's code, design guide and references. Before publishing, ask Max to replace the site's purchase links with your affiliate links: the code arrives with the links the producer wrote into it, and the package does not change them. Otherwise buyers who click to purchase go to the producer's checkout and the sale is not attributed to you. Then open the project and click Publish: until then, those funnel steps have no live page. You can keep editing with Max; the conversation starts from scratch. See Max Design.

      The funnel arrives laid out exactly as the producer built it: the connections between steps (quiz exits included), the automations connected to pages, the drawings on the canvas and the card arrangement in Analytics.

      The exception is an automation started by a purchase, cart or checkout event of an offer that did not come with you (not shared, or without an approved affiliation). That connection is removed during the import so the automation does not fire on every sale in your account. After you choose the step's offer, connect the trigger to the automation again on the canvas.

      Page images are copied into your account: if the producer deletes a file later, your pages are not affected. Images the producer loads from another website still come from there. These copies belong to the imported pages and do not show up in your media library.

      5. Connect your accounts

      WhatsApp number, Telegram bot, Instagram account, email sender and AI agent on a channel belong to each person and do not come in the package. When a package automation used one of the producer's accounts, it arrives without the account, and the step or trigger that depended on it stays paused: the automation cannot be activated (not even by the published funnel) while such a step remains.

      In Shared Packages → Imported packages, the package shows the Connect to activate panel, with one row per producer account and the automations that used it:

      • Pick your account and click Connect. Your account goes only into the steps and triggers that used the producer's, and it also fills the other rows of the same type in this package. If you have a single account of that type, it is already selected.
      • Set up later takes the row off the panel; you pick the account directly in the automation editor. Picking the account in the step also clears the pending state: the row then shows Account picked in the automation editor.
      • Attendants and AI keys also show up in the panel, for the package's teams, pipelines, schedules and AI agents.
      • An AI agent on a channel is chosen in the automation editor.

      Stage automations of a pipeline and reminders of a schedule from the package also show up in the panel when they used one of the producer's accounts. A condition in an automation's Goal that used a producer account arrives empty and does not show up in the panel: until you pick your account in the Goal, that condition is never met.

      WhatsApp templates

      A WhatsApp template belongs to each person's number, so every template the producer used shows up as its own row in the panel. You have two options:

      • If you already have an approved template with the same name and language, pick it in the row and click Connect.
      • Click Create my templates from the package ones. Clickmax shows the text of each template; review it, untick any you don't want, pick the number and click Send for approval. The templates are created on your number with the same text and sent to WhatsApp for approval. Nothing is sent without this confirmation. When you connect a WhatsApp number in the panel, this window opens with that number already selected.

      While WhatsApp reviews them, the row shows Template submitted and the step stays paused. Once a template is approved, it goes into the step on its own and the row leaves the pending list. If WhatsApp does not approve it, the row shows the reason: fix the template in Message templates and submit it again, or pick another approved template of yours. To use a template with a different name, pick it directly in the step, in the automation editor.

      If the number already has a template with the same name and different text, it is not created again: pick yours from the list. Packages published before this option do not carry the template text; in that case, pick the template in the automation editor.

      While an account is still missing, the funnel editor shows a notice at the top, and the automation editor shows another with how many steps still use a producer account.

      To pick an account, you need access to it in automations. After connecting, activate the automation or publish the funnel again.

      6. Customise before promoting

      This is the step that separates the affiliates who sell from the ones who do not:

      • Set up your tracking. The funnel arrives without a Pixel or Google Analytics: the producer's stay in the producer's account. See end-to-end tracking.
      • Choose your quiz, calendar and webchat, if you left any for later during the import. A quiz, calendar or webchat the producer did not include in the package does not come along, so those steps arrive in the funnel with the notice Choose one of your quizzes (or calendars, or webchats). Click Choose quiz on the card, pick one of yours or create a new one, and publish the funnel again. Until the step has one of yours, it is not published and its triggers do not start automations.
      • Fill in your authentication in automations with an HTTP Request. They arrive without the producer's credentials: the step is highlighted in the editor, and the automation does not activate until you fill in your own key, token or webhook URL.
      • Adjust the copy to your voice and your audience.
      • If the funnel has an external page, it arrives pointing to the producer's address. Open the step and replace it with the URL of your external page.
      • Confirm the affiliate link is correct, otherwise the commission is never recorded.
      • Check the checkout. It arrives the way the producer built it (design, steps and order bumps), already using the offers chosen during the import. An order bump whose offer is not in the package only comes along if you can already sell that offer; if none is left, the order bump arrives turned off. The address buyers are sent to after paying and the link of the decline button are not part of the package: if you want them, set them to your own pages.
      • If the producer did not share the offer and you picked one of your own, the package's automations switch to your offer and its product. This covers triggers, the Goal, offer or product conditions and the offer of the card created by Assign opportunity. If another offer of the same product stays shared, product filters keep the producer's product, because sales of that offer still belong to it.
      • Review the automations. The tags, lists, senders and numbers you choose during the import must belong to your account. The AI SDR block arrives without the AI assignment, the Connection and the Approved template: choose your own before publishing.

      7. Test the whole purchase

      Walk the funnel through to payment and confirm the sale is attributed to you.

      8. Keep it up to date

      When the producer publishes a new version, you get the New package version notification, and the package shows Version N available in Shared Packages → Imported packages. Click See what changed to see each funnel, page and automation that changed, was added or left the package.

      • Update on their own lists the items that changed and that you did not edit or put live. The new version replaces your copy.
      • Choose what to do lists the rest. An item that changed and that you edited (or that is live: a published page or funnel, an automation that is on) can stay as it is (Keep mine) or be replaced (Use the new version). An item that left the package can stay (Keep mine) or be deleted (Delete mine). Without a choice, the item stays as it is.
      • Items that are new in the package are created in your account.

      Click Update to version N. The update runs in the background and can take a few minutes. If something fails along the way, what it created is undone and your copy stays as it was; the package shows The last update did not finish, and you can try again.

      The new version of an item arrives as it did on import: automations off, and the funnel and pages to publish again. The new page keeps the old page's address, and the funnels and automations you kept point to the new pages, funnels and automations (an active automation that fired on the old page keeps firing on the new one). The accounts you already connected in Connect to activate go into the new automations on their own; if a new automation uses an account you have not connected yet, it shows up in that panel. Items that came along and you already have (quiz, custom field, pipeline…) stay the same, and new ones are created. Your Max Design project also stays as it is: changes the producer made to their project do not reach yours, and a Max Design project that is new in the package is created in Marketing → Max Design.

      In the Imported packages tab, each package shows the producer's version you imported. A package imported before Clickmax started recording that version shows the notice This package will not get updates when you open it. To get new versions again, click Import again: the import creates a new copy, and your current copy stays as it is.

      If it didn't work

      • The link has expired or is invalid: ask whoever shared it for a new one.
      • You see This package has not been published by the producer yet: the producer has not published a version of the package. Ask them to publish it and try again.
      • The import was refused because you cannot become an affiliate of an offer: switch that offer to one of yours with Use my own offer, or ask the producer to turn the product's affiliation back on or lift your suspension.
      • You cannot get into the import: check your role in who can do what.
      • The sale was not attributed to you: review the affiliate link you promoted.
      • The import refused the package saying your account does not have Max Design: the package includes Max Design pages and your access needs to include Max Design.
      • A step with a Max Design page does not open: publish the imported project in Marketing → Max Design.
      • Nobody can book through the imported schedule: pick who attends in the schedule and turn its public link on.
      • The imported automation does not activate and the editor flags a step with "came from a package and used the producer's account": connect your account in Shared Packages → Imported packages or pick the account in the step.
      • An imported automation does not fire, or a filter shows no value: it used one of the producer's segments, broadcasts, capture links or Instagram posts. Open the automation and choose the equivalent from your account.
      • A quiz, calendar or webchat step stays in draft after you publish: it does not have a quiz, calendar or webchat of yours yet. Use Choose on the step's card and publish again.
      • The automation does not activate and shows Flow has incomplete HTTP request node(s): open the highlighted HTTP Request step and fill in your own authentication.
      • An automation block fails saying it uses an item from another workspace: the block points to a tag, list, contact field or pipeline that is not in your account, and nothing was written to the contact. Open the block, pick one of your own items and try again. See Why is a block in my automation failing?.