Cyclr is the third party that we use to build our bridges. We use Cyclr because their system enables users who do not know much about code, to create data integrations. The way they do this is by creating what Cyclr calls “connectors''. Connectors are the building blocks that Cyclr provides to its users to be able to connect different APIs. You can think of them as a visual (although digital) representation of an API.
After the bridge request form is submitted, we will gather the additional information we need to see if the bridge can be built. The first step in this process is checking to see if Cyclr already has a connector built into the system.
If Cyclr has already created a connector for the system we are trying to bridge into, this expedites our process and we can test the connector to see if we can get the information we want from the API.
If Cyclr doesn’t have a connector created for the system, we need to gather a bit more information, and send it over to cyclr so they can determine if a cycle can be built, if it can get the information we need from it, and if so, build the connector. This can take many weeks depending on the system.
If Cyclr already has a connector, or if they determine that they can build the connector, we will then test the connection to make sure we can get the data we want in a format that we want.
If Cyclr doesn't have a connector, and determines that they cannot access the API, or the information available from the API isn't formatted in a way that meets our needs, we will mark the bridge as a dead bridge and recommend the bridge fee be refunded.
The Analytics Director, or someone that the Analytics Director has designated, will confirm they agree with the recommendation to refund the client, and then the PM will make the refund request.
To get access to Cyclr, contact your PM. If you’re a PM who doesn’t know how to give access to Cyclr, reach out to your VP of PM who should be able to give you access or point you in the direction of someone who can.