Aident logoAident logo centerAident Loadout
Use CasesPricingDocs
ENStart Now
AppsCustomer.io ToolsCustomerio Track Screen
Customer.io Tools

Customerio Track Screen

Track mobile screen views in Customer.io for analytics and user journey tracking. Records when a user views a screen in your mobile app. Use this when you need to: - Track user navigation patterns in mobile apps - Record screen views for engagement analytics - Trigger workflows…

Write actionRisk level 2 of 5API key connection
Use Customerio Track Screen

Pricing and limits

Aident logo

Product

Aident LoadoutAident Playbook EditorOpen-CUAK

About

AppsSkillsUse CasesDocsBlogPricingDownloadsPrivacy PolicyTerms of Service

Alternatives

vs Composiovs Zapier
llms.txtGet an AI summary of Aident LoadoutSummarize with ChatGPTSummarize with ClaudeSummarize with GeminiSummarize with Perplexity

© Aident Labs, 2024-2026

Pricing
Free
Unified payment
Not currently supported

Inputs

  • namestring
    Required
    Name of the screen that was viewed (e.g., 'home_screen', 'feed', 'settings').
  • typestring
    Event type identifier. Should always be 'screen' for screen view events.
  • sentAtstring
    ISO 8601 timestamp of when the event was sent from the client. Used for clock skew correction.
  • userIdstring
    Unique identifier for a known user. Use this to track screen views for identified users. Mutually exclusive with anonymousId - provide one or the other.
  • contextobject
    Optional contextual information about the event (e.g., device info, IP address, app version).
  • versionnumber
    Version number of the tracking spec being used.
  • messageIdstring
    Unique identifier for this message/event. If not provided, one will be generated automatically.
  • timestampstring
    ISO 8601 timestamp of when the screen view occurred. If not provided, the current time will be used. Format: YYYY-MM-DDTHH:mm:ss.sssZ
  • propertiesobject
    Optional key-value pairs containing additional context about the screen view (e.g., screen_category, platform, referrer).
  • receivedAtstring
    ISO 8601 timestamp of when the event was received by the server. Typically set automatically.
  • anonymousIdstring
    Unique identifier for an anonymous user who hasn't been identified yet. Mutually exclusive with userId - provide one or the other.
  • strict_modeboolean
    When True, enables strict validation that returns proper HTTP error codes (400/401) for validation failures. When False (default), the API operates in permissive mode, logging errors but returning HTTP 200.

Observable output

  • data
    Required
    Data from the action execution
  • errorstring
    Error if any occurred during the execution of the action
  • successfulboolean
    Required
    Whether or not the action execution was successful or not

Skills that use this Action

Related use cases

No verified related use cases are linked yet.

Official source

Provider source

Skills that use this Action

No published Skills explicitly reference this Action yet.