Skip to main content

FullStory integration

Data and analytics connector, available on Zeplik

FullStory is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect FullStory and Zeplik can act on your data and analytics for you: FullStory provides digital experience analytics APIs for managing users, events, sessions, exports, recording settings, privacy rules, and related. You stay in the conversation while the assistant does the work in FullStory directly.

Zeplik exposes 18 read actions and 12 write actions for FullStory. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in FullStory without your consent.

Try FullStory on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

What Zeplik can do with FullStory

Read from FullStory (18)

Runs automatically in any conversation.

  • Get account

    Validate the connected API key and return its FullStory organization, identity, and API-key role. Do not use the role to infer paid product entitlements.

  • Get element block

    Get one FullStory privacy element-block rule by ID, including its exact selector source, recording or masking operation, platforms, and editability. Warning: this exposes privacy-sensitive recording configuration. This API is in beta; functionality and documentation are subject to breaking change without notification.

  • Get extraction rule

    Get one FullStory beta extraction rule by ID, including its archive state and complete nested source and mappings.

  • Get import status

    Get status and success/error counts for an asynchronous FullStory event or user import job.

  • Get operation

    Get detailed status, progress, operation-specific results, and failure details for one asynchronous FullStory operation.

  • Get organization quotas

    Return current FullStory session and server-event quota usage, limits, and quota periods.

  • Get recording settings

    Get one current FullStory recording-settings category. Privacy settings may contain sensitive configuration and large built-in rule sets; the complete provider response is preserved.

  • Get segment

    Get metadata and the FullStory app URL for one segment.

  • Get user

    Retrieve one user by FullStory-generated user ID, including profile fields and a FullStory app link.

  • List datasets

    List beta datasets readable by the connected FullStory organization.

  • List element blocks

    Return one page of custom and built-in FullStory privacy element-block rules. These rules determine what FullStory records or masks.

  • List extraction rules

    List all FullStory beta extraction rules matching one required scope and optional filters, together with current active-rule usage and limits.

and 6 more.

Act in FullStory (12)

Runs only after you enable write access.

  • Cancel operation

    Irreversibly request cancellation of a cancelable in-progress FullStory operation, currently intended for segment exports. Confirm the operation before calling because a successful cancellation request cannot be undone.

  • Create annotation

    Add a persistent annotation to the FullStory timeline for a point or time range. Warning: FullStory provides no matching delete endpoint, so a successful call cannot be cleaned up through this API.

  • Create element block

    Create a beta FullStory element recording or masking rule. Requires an Admin API key. Privacy-critical: an incorrect selector, UNMASK action, or live scope can expose sensitive data, while EXCLUDE or MASK can suppress useful recording. Review every field and prefer preview scope before calling.

  • Create extraction rule

    Create and immediately activate one FullStory beta extraction rule using the provider's nested rule, source, and mapping contract. Extraction can capture sensitive element, URL, header, or body values and can materially increase collected data volume. Archiving later only stops future capture; it does not erase data already collected. Review selectors, network filters, mapping targets, property scope, and privacy policy before calling. The beta contract may change without notice. Requires an Architect or Admin API key.

  • Delete element block

    Permanently delete a custom FullStory privacy element-block rule. This is irreversible: removing a block or mask can expose sensitive content in future recordings. Confirm the exact custom rule first; built-in rules cannot be deleted. This API is in beta and may change without notice.

  • Delete user data

    Permanently delete a FullStory user and their associated data by FullStory-generated ID. This is an irreversible privacy mutation; confirm the target before calling.

  • Import events

    Start an asynchronous import of 1 to 50,000 server events. This permanently adds analytics data; use an idempotency key when retrying.

  • Import users

    Start an asynchronous upsert import of 1 to 50,000 users. This mutates personal profile data.

  • Set extraction rule archived

    Archive a FullStory beta extraction rule to stop future capture, or unarchive it to resume capture. Warning: this changes collection behavior immediately. Archiving does not erase data already collected, and data not captured while the rule is archived cannot be recovered by unarchiving. Confirm the rule ID and intended state before calling. Requires an Architect or Admin API key.

  • Update element block

    Fully replace an editable beta FullStory element recording or masking rule. Requires an Admin API key. This is an irreversible privacy configuration update, not a patch: read the existing rule first and provide every required replacement field. An incorrect selector, UNMASK action, or live scope can expose sensitive data, while EXCLUDE or MASK can suppress desired recording.

  • Update extraction rule

    Partially update a FullStory beta extraction rule using last-write-wins semantics. Provide at least one of name, description, source, or mappings. Omitted fields remain unchanged; read the current rule first. Warning: changing a rule's source or mappings changes what FullStory captures and may affect privacy, downstream analytics, and data volume.

  • Upsert user

    Create or update one FullStory user. Supplying fullstory_user_id updates that record; otherwise uid identifies an upsert. This mutates personal profile data.

How to connect FullStory

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try FullStory immediately.

  2. Connect FullStory

    Open Settings and go to Connectors, then press Connect on FullStory. You can also connect from the FullStory page in the app.

  3. Add your FullStory API key

    Paste your FullStory API key when prompted. Zeplik stores it securely on the server and starts working with FullStory right away.

Frequently asked questions

Can I use FullStory with Zeplik?
Yes. FullStory is available as an integration on Zeplik. Connect it once and the AI assistant can work with your FullStory account inside any conversation.
What can Zeplik do with FullStory?
Once connected, Zeplik has 18 read and 12 write actions for FullStory. FullStory provides digital experience analytics APIs for managing users, events, sessions, exports, recording settings, privacy rules, and related.
How do I connect FullStory to Zeplik?
You connect FullStory by pasting your own FullStory API key in Settings under Connectors. There is no separate app to install.
Does Zeplik change things in FullStory without asking?
No. Zeplik reads from FullStory by default. Any action that changes data in FullStory requires write access, which stays off until you enable it in Settings under Connectors.
How much does connecting FullStory cost?
Connecting FullStory is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.

Related data and analytics integrations

More on Zeplik

Connect FullStory to your AI assistant

Every model, one chat. Bring FullStory into Zeplik and let the assistant do the work.