Mismatch in the Activity types received from Rest API | Community
Skip to main content
A
Anonymous
October 5, 2016
Question

Mismatch in the Activity types received from Rest API

  • October 5, 2016
  • 1 reply
  • 3479 views

Hi,

Trying to retrieve the Activity types using the service /rest/v1/activities/types.json

In the response found that i received only 53 activity types (Attached the response - ActivityTypesResponse.json)

When seen in the Marketo login could see more activity types (near to 70).

To give an example - "Add to Segment" is not being returned (Attached the screenshot showing one of the missing activity highlighted - MissingActivity.png).

Can you please help to find the reason for the mismatch

Endpoint: 607-VUD-713.mktorest.com/rest

Identity: 607-VUD-713.mktorest.com/identity

Thanks,

Kiran

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

A
Anonymous
October 5, 2016

"Clicked Link on web page" in the UI is "Click Link" returned from the API:

{
      "id": 3,
      "name": "Click Link",
      "description": "User clicks link on a page",
      "primaryAttribute": {
        "name": "Link ID",
        "dataType": "integer"
      },
      "attributes": [
        {
          "name": "Client IP Address",
          "dataType": "string"
        },
        {
          "name": "Query Parameters",
          "dataType": "string"
        },
        {
          "name": "Referrer URL",
          "dataType": "string"
        },
        {
          "name": "User Agent",
          "dataType": "string"
        },
        {
          "name": "Webpage ID",
          "dataType": "integer"
        }
      ]
    }

What other activity types are you not seeing?

    A
    Anonymous
    October 5, 2016

    Thanks Jason for your prompt response.

    My bad.. I gave a wrong activity type which is in the response.

    "Add to Segment" is missing.  Did edit the discussion as well stating that "Add to Segment" is missing.

    Thanks,

    Kiran

    A
    Anonymous
    October 5, 2016

    I imagine the API would report that as a "Change Segment" event, probably from NULL to a new segment:

    {
          "id": 108,
          "name": "Change Segment",
          "description": "Change segment (within a segmentation) for a lead",
          "primaryAttribute": {
            "name": "Segmentation ID",
            "dataType": "integer"
          },
          "attributes": [
            {
              "name": "New Segment ID",
              "dataType": "integer"
            }
          ]
        }
      Terms & ConditionsAccessibility statement

      Loading footer...