> ## Documentation Index
> Fetch the complete documentation index at: https://help.influocial.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# Share your campaign page and collect applications

> Publish a campaign page that creators can discover and apply to directly — no Influocial account required on their end. Collect inbound proposals at scale.

When you publish a campaign in Influocial, it gets a public page that you can share anywhere. Creators can read your brief, check deliverable requirements and compensation, and submit a proposal — all without needing to create an account. This lets you collect inbound applications from creator communities, social channels, and direct outreach at the same time.

## What creators see on the page

Your public campaign page shows creators everything they need to decide whether to apply. The page includes:

* **Campaign overview** — your brand, product, and campaign goal
* **Product details** — what is being promoted and any relevant context
* **Deliverable requirements** — formats, quantities, and any creative direction
* **Deadline** — content due date and expected posting window
* **Usage rights** — whether content will be used for organic posts, paid ads, or whitelisting
* **Compensation** — gifted product, fee, or both

<Note>
  Creators do not need to create an Influocial account to view your campaign page or submit a proposal. This removes friction and increases the volume of quality applications you receive.
</Note>

## Share your campaign with creators

<Steps>
  <Step title="Publish your campaign">
    Complete your campaign setup and click **Publish**. Your campaign page goes live immediately with a unique shareable link.
  </Step>

  <Step title="Copy your campaign link">
    From the campaign workspace, copy the public campaign link. You'll find it in the campaign settings or at the top of the published page.
  </Step>

  <Step title="Share it across your channels">
    Distribute the link wherever your target creators are active:

    * Creator communities and Facebook groups
    * Your brand's Instagram, TikTok, or Twitter/X
    * Creator newsletters or Substack communities
    * Direct message to creators you've already identified
  </Step>

  <Step title="Invite specific creators directly">
    If you have creators in mind, send them the campaign link directly by email or DM. They land on the same public page as any other applicant and submit through the same flow.
  </Step>

  <Step title="Review applications as they arrive">
    Each application lands in the **Applied** stage of your campaign pipeline. From there, you can review proposals, compare creators, and move the strongest fits to **Shortlisted**.
  </Step>
</Steps>

## Best practices for higher-quality applications

<Tip>
  Use clear, friendly language in your brief — write as if you're explaining the campaign to a creator you've just met, not drafting a legal brief. Briefs that specify what great content looks like (with examples or references) attract creators who already understand your brand. Once strong applicants come in, respond quickly — top creators often have multiple brand conversations active at the same time and will prioritise the brand that moves fastest.
</Tip>

<AccordionGroup>
  <Accordion title="Be specific about what great content looks like">
    Vague briefs attract vague proposals. Include a reference video, a list of must-mention points, or a link to a past campaign you loved. Creators apply with more confidence and deliver content closer to brief on the first pass.
  </Accordion>

  <Accordion title="Set realistic deadlines">
    Build in buffer time between the content due date and your campaign end date. Creators appreciate flexibility, and you'll have time to request revisions without rushing.
  </Accordion>

  <Accordion title="Keep compensation transparent">
    Whether you're offering gifting, payment, or both, state it clearly. Ambiguity around compensation is the most common reason creators abandon an application mid-way through.
  </Accordion>
</AccordionGroup>