Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Rokt Connector: Support All Rokt Account Timezone Options

Answered
Jonathan Roketenetz User

Which connector?: Rokt

Additional details: 

  • The Rokt Fivetran connector's timezone selection directly controls how Rokt aggregates metrics (impressions, conversions, spend) into daily/hourly buckets
  • If a timezone a business has their Rokt account configured to is unsupported in connector configuration options, businesses receive data bucketed into incorrect time windows. Currently, only America/Chicago, Pacific/Honolulu, and Australia/Sydney are supported. In my case, our Rokt account is configured to America/New_York.
  • The required workaround (UTC → wrong local TZ → correct local TZ → UTC) adds fragility, documentation burden, and is easy to get wrong. It's a blocker to being able to use the connector in my case.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Syead Mujtaba Imam Rizwi Fivetranner

    Hi Jonathan,

    Thank you for the request. We have added this to our active backlog. We have confirmed that the Rokt API supports flexible timezone configuration, so expanding beyond the current three supported options appears technically feasible. Which timezones are most critical for your setup? Knowing this will help us prioritize the right ones. We will keep you updated on this thread as we make progress.