Geotab Data Connector Access

The Geotab Data Connector uses the OData protocol to connect your fleet data to supported BI tools. Access requires your MyGeotab credentials in a specific format.

The Geotab Data Connector uses the OData protocol to authenticate with your MyGeotab credentials. Your username must be in the format <MyGeotab Database Name>/<MyGeotab Username> and your password is your MyGeotab password.

Data obtained from the connector is stored and cached locally within your BI tool file. Refresh your data daily to access the latest information.

Finding your Data Connector access URL

The access URL for the Geotab Data Connector differs depending on your BI tool. Power BI and Excel use a unified URL, while Tableau requires a server-specific URL.

To find your access URL, open the Geotab Data Connector Add-In page in MyGeotab. The Add-In displays the correct URL for your database.

Geotab Data Connector Add-In page in MyGeotab showing the access URL
Important:

Power BI and Excel support server redirection and use a single unified access URL. Tableau does not support server redirection and requires a server-specific URL containing your database's server number. Use the URL shown in the Geotab Data Connector Add-In for your tool.

Use the following login details when prompted by your BI tool:

  • Username: <MyGeotab Database Name>/<MyGeotab Username>

  • Password: your MyGeotab password

The following examples show how MyGeotab credentials map to Data Connector login details.

Power BI and Excel

MyGeotab login details

Data Connector login details

  • Database name: other_dbname

  • Username: email@domain.com

  • Password: SecurePassword1234

  • Access URL: https://data-connector.geotab.com/odata/v4/svc/

  • Username: other_dbname/email@domain.com

  • Password: SecurePassword1234

Tableau

MyGeotab login details

Data Connector login details

  • Data Connector server: 1

  • Database name: geotab_dbname

  • Username: email@domain.com

  • Password: SecurePassword1234

  • Access URL: https://odata-connector-1.geotab.com/odata/v4/svc/

  • Username: geotab_dbname/email@domain.com

  • Password: SecurePassword1234

Filtering Data Connector data by date range

Apply date range filters to your access URL to improve performance and limit the data returned to your BI tool.

For operational reporting, apply date range filters to specific tables in your access URL. Filters pre-filter data on the server before returning results to your BI tool, which results in faster data returns. The date range filter applies to the local date or datetime based on the timezone setting of each telematics device in MyGeotab.

The Geotab Data Connector supports two types of date range filters:

  • Absolute date range: recommended for ad-hoc or static analyses with a fixed start and end date.

  • Relative date range: recommended for regularly-refreshed dashboards that always display the most recent data.

When using date range filters, you must explicitly name the table in the access URL:

  • Power BI and Excel: https://data-connector.geotab.com/odata/v4/svc/[tableName]?$search=<dateRange>

  • Tableau (server <serverNumber>): https://odata-connector-<serverNumber>.geotab.com/odata/v4/svc/[tableName]?$search=<dateRange>

Only historical or date-based tables support date range filters. The following tables are supported:

  • VehicleKpi_Daily

  • VehicleKpi_Monthly

  • LatestVehicleMetadata

  • DriverKpi_Daily

  • DriverKpi_Monthly

  • FleetSafety_Daily

  • VehicleSafety_Daily

  • DriverSafety_Daily

  • FaultMonitoring_Daily

Absolute date range filters

Use an absolute date range filter to pre-filter data for a fixed date range before it is returned to your BI tool.

Absolute date ranges filter data for a specific fixed period. Use this for ad-hoc or static analyses. There are two methods:

Method 1: Specify a from and to date Method 2: Specify only a from date

  • Filters for records with a local date between the specified from and to dates.

  • Syntax:from_yyyy-MM-dd_to_yyyy-MM-dd

  • Filters for records with a local date between the specified from date and the newest available date.

  • Syntax:from_yyyy-MM-dd

Examples

Power BI and Excel users should use the simplified subdomain https://data-connector.geotab.com in their access URL.

Scenario

Access URL

Date range filter

  • Data Connector Server: 1

  • Desired table: VehicleKpi_Daily

  • From date: 2022-01-05

  • To date: 2022-01-19

https://odata-connector-1.geotab.com/odata/v4/svc/VehicleKpi_Daily?$search=from_2022-01-05_to_2022-01-19

?$search=from_2022-01-05_to_2022-01-19

  • Data Connector Server: 2

  • Desired table: VehicleKpi_Hourly

  • From date: 2022-01-23

  • To date: most recent

https://odata-connector-2.geotab.com/odata/v4/svc/VehicleKpi_Hourly?$search=from_2022-01-23

?$search=from_2022-01-23

Relative date range filters

Use a relative date range filter to display a rolling window of the most recent data in your regularly-refreshed dashboards.

Relative date ranges filter data for a rolling window of time, so your dashboards always display the most recent information. Use this for regularly-refreshed dashboards.

Syntax: <positionKeyword>_<number>_<datePart>

When the number is 1, it can be omitted: <positionKeyword>_<datePart>

Supported position keywords

  • this (or these): includes the current partial period

  • last: excludes the current partial period, returning only complete periods

Supported date parts

  • day

  • week

  • month

  • year

Syntax for dateRange

<positionKeyword>_<number>_<datePart>

Note that when the <number> argument is 1, it can be completely omitted and changed to <positionKeyword>_<datePart> for convenience

Examples

Power BI and Excel users should use the simplified subdomain https://data-connector.geotab.com in their access URL.

Scenario

Access URL

Date range filter

  • Data Connector Server: 1

  • Desired table: VehicleKpi_Monthly

  • Today's date: 2022-01-23

  • Desired date range: year-to-date

https://odata-connector-1.geotab.com/odata/v4/svc/VehicleKpi_Daily?$search=this_1_year

?$search=this_1_year

  • Data Connector Server: 1

  • Desired table: VehicleKpi_Monthly

  • Today's date: 2022-01-23

  • Desired date range: last complete year (calendar year 2021)

https://odata-connector-1.geotab.com/odata/v4/svc/VehicleKpi_Daily?$search=last_1_year

?$search=last_1_year

  • Data Connector Server: 1

  • Desired table: VehicleKpi_Daily

  • Today's date: 2022-01-23

  • Desired date range: month-to-date

https://odata-connector-1.geotab.com/odata/v4/svc/VehicleKpi_Daily?$search=this_1_month

?$search=this_1_month

  • Data Connector Server: 1

  • Desired table: VehicleKpi_Daily

  • Today's date: 2022-01-23

  • Desired date range: most-recent 3 months (Nov 2021, Dec 2021, Jan 2022)

https://odata-connector-1.geotab.com/odata/v4/svc/VehicleKpi_Hourly?$search=these_3_month

Note: this_3_month will also work

?$search=these_3_month

  • Data Connector Server: 2

  • Desired table: VehicleKpi_Daily

  • Today's date: 2022-01-23

  • Desired date range: most-recent 3 complete months (Oct 2021, Nov 2021, Dec 2021)

https://odata-connector-2.geotab.com/odata/v4/svc/VehicleKpi_Hourly?$search=last_3_month

?$search=last_3_month

  • Data Connector Server: 2

  • Desired table: VehicleKpi_Hourly

  • Today's date: 2022-01-23

  • Desired date range: last 14 days

https://odata-connector-2.geotab.com/odata/v4/svc/VehicleKpi_Hourly?$search=last_14_day

?$search=last_14_day

Note:

OData pagination is handled automatically by Power BI, Excel, and Tableau. If you are using a custom script, you must handle pagination manually. For details, see the GDC ETL User Guide.

Selecting specific columns with $select

Use the $select query option to choose which columns are returned by your access URL.

The $select query option returns only the columns you specify from a table. Selecting fewer columns reduces the amount of data transferred and improves performance.

Add $select to your access URL:

  • Power BI and Excel: https://data-connector.geotab.com/odata/v4/svc/[tableName]?$select=[Column1],[Column2],...

  • Tableau (server <serverNumber>): https://odata-connector-<serverNumber>.geotab.com/odata/v4/svc/[tableName]?$select=[Column1],[Column2],...

Example

Scenario

Access URL

  • Data Connector server: 1

  • Desired table: DeviceGroups

  • Columns needed: CompanyGuid, GroupId, GroupName, ImmediateGroup, SerialNo, DeviceId

https://odata-connector-1.geotab.com/odata/v4/svc/DeviceGroups?$select=CompanyGuid,GroupId,GroupName,ImmediateGroup,SerialNo,DeviceId

Filtering records with $filter

Use the $filter query option to return only records that match the conditions you set.

The $filter query option returns only the records that match the conditions you set, similar to a WHERE clause in SQL.

Add $filter to your access URL:

  • Power BI and Excel: https://data-connector.geotab.com/odata/v4/svc/[tableName]?$filter=[Expression]

  • Tableau (server <serverNumber>): https://odata-connector-<serverNumber>.geotab.com/odata/v4/svc/[tableName]?$filter=[Expression]

Important:

Each query supports only one $filter parameter. Combine multiple conditions with logic operators instead of adding more $filter parameters.

Comparison operators

A filter expression consists of a case-sensitive column name, a lowercase comparison operator, and a value matching the column's data type.

Operator

Meaning

eq

Equals

ne

Not equals

gt

Greater than

ge

Greater than or equal to

lt

Less than

le

Less than or equal to

You can combine multiple filter expressions using the logic operators and, or, and not. The not operator must precede a boolean column or expression in parentheses, for example not (DeviceId eq 'abc'), not not DeviceId eq 'abc'.

Examples

Scenario

Access URL

  • Data Connector server: 1

  • Desired table: LatestVehicleMetadata

  • Filter: LastGps_Speed greater than 3

https://odata-connector-1.geotab.com/odata/v4/svc/LatestVehicleMetadata?$filter=LastGps_Speed gt 3

  • Data Connector server: 2

  • Desired table: VehicleKpi_Daily

  • Filter: Local_Date on or after a specific date

https://odata-connector-2.geotab.com/odata/v4/svc/VehicleKpi_Daily?$filter=Local_Date ge '2025-01-01'

  • Data Connector server: 1

  • Desired table: DeviceGroups

  • Filter: DeviceId in a list, ImmediateGroup equals true, and DeviceId not equal to a value

https://odata-connector-1.geotab.com/odata/v4/svc/DeviceGroups?$filter=DeviceId in ('b14FA') and ImmediateGroup eq true and DeviceId ne 'b14FA1'

  • Data Connector server: 2

  • Desired table: LatestVehicleMetadata

  • Filter: LastGps_Speed greater than 3, and either Year or Model is not null, and Engine is not null

https://odata-connector-2.geotab.com/odata/v4/svc/LatestVehicleMetadata?$filter=LastGps_Speed gt 3 and (Year ne null or Model ne null) and Engine ne null

  • Data Connector server: 2

  • Desired table: DeviceGroups

  • Filter: DeviceId is not a specific value

https://odata-connector-2.geotab.com/odata/v4/svc/DeviceGroups?$filter=not (DeviceId eq 'b14FA')

Data types and formats

Data type

Format

String

Enclose the value in single quotes, for example '2025-09-24'. To include a single quote in a value, use two single quotes: 'O''Reilly'.

Date

Use the format YYYY-MM-DD, for example 2025-09-23.

Datetime

Use the format YYYY-MM-DDTHH:MM:SSZ, for example 2025-09-23T22:00:00Z. Use date(datetime) for comparisons, for example date(datetime) eq 2025-09-24, to avoid precision and time zone differences.

Integer

Whole numbers, for example 1 or 100.

Double

Decimal numbers, for example 1.1. Use round(double) when comparing, for example round(double) eq 1.

Boolean

Case insensitive: true, True, and TRUE are equivalent.

Null

Case sensitive: only null is valid. Works only with the eq and ne operators.

Arrays accept only literal values, not columns or functions. Use arrays with string, date, or integer values. Avoid double values in arrays, and use round() instead.

Restrictions

  • Each query supports only one $filter parameter.

  • Filtering on CompanyGuid is not allowed.

  • Filter values for GroupId, DeviceId, and DriverId must be within your access scope. Values outside your access scope are ignored.

  • Expressions such as column not in ('xxx') are invalid. Use not (column in ('xxx')) instead.

  • Special characters, such as &, must be URL-encoded, for example & becomes %26.

  • A single query supports up to 100 columns, parameters, or array values.

  • Column filters cannot override the default search date range. Make sure filter date values fall within the available date range for the query.

  • String comparisons support only eq, ne, or in for arrays, for example deviceId eq 'abc' or deviceId in ['abc','xyz'].