Control where your Pin appears, who sees it, and when it goes live. These settings are on your Pin's settings page in Studio — you'll land here after clicking Publish & Target in the Builder, or by selecting a Pin from Experiences > Pins.

Schedule your Pin

You can set a start and end time to automatically publish and unpublish your Pin.

1. Open the Schedule section on the settings page.
2. Under Starts, choose At a scheduled time and set a date and time. Leave it as When I publish to control this manually.
3. Under Ends, choose At a scheduled time and set an end date. Leave it as When I unpublish to keep the Pin live indefinitely.

You can always override a schedule by manually clicking Publish or Unpublish on the settings page. See Schedule experiences for more details.

Set page targeting

Page targeting controls where in your app the Pin appears — which URLs and which domains.

1. Open the Page Targeting section.
2. Under Path, choose where the Pin shows:

• All pages: The Pin appears on every page where Appcues is installed. Useful for Pins attached to global UI elements like a navigation bar or sidebar.
• Specific pages: Set URL path conditions using "starts with," "contains," "equals," or "matches regex." For example, to show a Pin only on settings pages, set the path to contains /settings.vIf your URLs include dynamic segments (like user IDs or account slugs), use contains for the stable part or matches regex for more complex patterns. See Page Targeting for detailed instructions on dynamic URLs and regex.

3. Under Domain, select which domains the Pin displays on (production, staging, etc.). By default, Pins show on all domains where Appcues is installed. To restrict a Pin to a single environment, select only that domain. See Manage Available Domains to add or manage domains.

Use the Test Page Targeting tool on the settings page to verify your URL and domain conditions match the pages you expect.

Set audience targeting

The audience section controls who sees your Pin.

1. Open the Audience section.
2. Choose one of three options:

• All users: Show the Pin to everyone in your application. Good for general-purpose help Pins like a "?" icon next to a confusing setting.
• Users in a segment: Target a saved segment. Use this when you already have a reusable audience defined (e.g., "Free trial users" or "Admins").
• Specific users: Build custom conditions using User Properties, Group Properties, Language, experience interactions (Flows, Pins, Banners, Checklists, Mobile Flows), Events, Segments, Emails, and Push notifications. Combine multiple conditions with All (AND) or Any (OR) logic. For example, to show a Pin only to users on a specific plan who haven't completed onboarding, add a plan property condition AND a Flow interaction condition.

See Audience Targeting for the full list of available conditions and operators.

Common targeting patterns

• Contextual help for a specific feature: Set page targeting to the feature's URL path. Set audience to All users. This places a persistent helper Pin right where the question comes up.
• Role-specific guidance: Set audience to Specific users with a condition like role equals admin. Attach the Pin to an element that only matters for that role (e.g., a billing settings link).
• Post-onboarding tips: Set audience to Specific users and add a condition like "Has completed" your onboarding Flow. This ensures the Pin only appears for users who've finished onboarding and are ready for deeper guidance.
• Testing before launch: Set the domain to your staging environment only, or set audience to a segment containing only internal testers. Publish the Pin, verify it works, then update targeting to production/all users.
• Multiple Pins on the same page: Pins don't conflict with each other or with Flows. Target as many Pin experiences to the same page as you need — qualifying users see all of them.

Confirm it worked

After publishing, verify your targeting is working:

• Open your app in the targeted environment and confirm the Pin appears on the correct page
• Check with a user who matches your audience conditions — and one who doesn't — to confirm targeting filters correctly
• Use the Diagnostics tool in Studio to check a specific user's eligibility for the Pin
• If you set a schedule, confirm the start/end times are in the correct timezone

Troubleshooting

Pin doesn't appear after publishing

• Open the Appcues Debugger and verify Appcues is installed on the page (all rows should show green checkmarks).
• Check that the current URL matches your page targeting conditions. Use the Test Page Targeting tool on the settings page.
• Verify the domain is included in your page targeting. If you're testing on staging but the Pin targets production only, it won't show.

Pin shows to the wrong users (or doesn't show to the right ones)

• Open the Diagnostics tool and look up the user. The eligibility panel shows which conditions pass or fail.
• Check that user properties are being sent correctly and match the casing in your conditions — values are case-sensitive (e.g., Admin ≠ admin).
• If using Any (OR) vs All (AND) logic, verify the conditions aren't mutually exclusive. For example, targeting pages containing "account" AND "dashboard" AND "payments" requires a single URL to match all three — use Any (OR) if you mean different pages.

Pin appears on pages it shouldn't

• Review your path conditions. A contains condition like /app will match /app/settings, /app/dashboard, and /application. Use equals or a more specific starts with value to narrow the match.
• Check if the domain targeting is set to All domains when it should be restricted.