{"id":87187,"date":"2024-12-08T05:09:29","date_gmt":"2024-12-08T13:09:29","guid":{"rendered":"https:\/\/rightwave.com\/rwi\/?page_id=87187"},"modified":"2024-12-11T02:41:02","modified_gmt":"2024-12-11T10:41:02","slug":"match-junk-value","status":"publish","type":"page","link":"https:\/\/rightwave.com\/rwi\/rdn-help\/advanced-services\/match-junk-value","title":{"rendered":"RDN Match Junk Value"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t

Implementation of RDN Webhook in Marketo\n<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

In this document, we will learn how to implement the RDN webhook to utilize different services. This example focuses on how to implement RDN services for country and state implementation.\n<\/p>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Service Name: Match Junk Value<\/b><\/h3>
  • Service Type<\/b>: Advanced Service<\/span><\/li>
  • Service Description<\/b>: The <\/span>Junk Lookup<\/b> service allows users to determine if a given input matches any of the predefined “Junk” values in a list. This is helpful when you need to flag or filter out specific records that fall into a category of unwanted or irrelevant data (e.g., countries, states, etc.). The service checks whether the input value matches any entry in the user-defined set of junk values.<\/span><\/li><\/ul>

    Use Case:<\/b><\/h3>
    • A user may have a list of countries, and they want to flag specific countries as “Junk” if they appear in that list. For example, the user may have predefined a list of 10 countries they consider “Junk” and wish to check if a newly entered country is part of this list.<\/span><\/li>
    • The user can submit a country as input and call the API to check whether this country exists in their pre-defined set of “Junk” countries. This allows the user to easily flag or filter out records that match the junk criteria.<\/span><\/li><\/ul>

      How It Works:<\/b><\/h3>
      1. Define Junk Values<\/b>: The user creates a list of junk values (e.g., countries, states, or any other data entries that are unwanted or irrelevant for the dataset).<\/span><\/li>
      2. API Request<\/b>: The user submits an input (e.g., a country name) and uses the <\/span>Match Junk Value<\/b> service to check whether the input matches any value in the predefined junk list.<\/span><\/li>
      3. API Response<\/b>: The service will return a result indicating whether the input is part of the junk set, enabling the user to mark the record as junk or take further action, such as excluding it from a report or dataset.<\/span><\/li><\/ol>

        Example Scenario:<\/b><\/h3>
        • The user has a list of 10 countries, like “United States”, “Canada”, “Mexico”, and others, defined as junk.<\/span><\/li>
        • A user submits “Canada” as input. The service will check if “Canada” exists in the junk list and return a match.<\/span><\/li>
        • If the service finds “Canada” in the junk list, the user can mark it as junk for processing or filtering purposes.<\/span><\/li><\/ul>

          This service helps streamline data validation processes, particularly when working with large datasets that require flagging irrelevant or unwanted records based on predefined criteria.<\/span><\/p>

          How To Use:<\/b><\/h3>

          Follow the below instructions to use the Match Junk Value service:<\/span><\/p>

          1. Click on Manage of Match Junk Value Service.<\/span><\/li><\/ol>

            \"\"<\/p>

            2) Click\u00a0 \u2018+\u2019\u00a0 to use Junk Value Lookup Service.\u00a0\u00a0<\/span><\/p>

            \"\"<\/p>

            1. Enter Junk Lookup Name.<\/span><\/li><\/ol>

              \"\"<\/p>

              1. You can choose any of the following, either CSV or Manual.\u00a0<\/span><\/li>
              2. CSV: Ensure there should be one column in CSV i.e. Junk Values. The first row of the CSV file is considered a column name. The rest of the rows are considered as data and there can be a maximum of 1,000 entries including the header.<\/span><\/li><\/ol>

                \"\"<\/p>

                1. Manual:\u00a0 Enter junk values manually as shown in the above image. <\/span>Then save the values.<\/li><\/ol>

                  \"\"<\/p>

                  1. Activate the Junk Value Lookup Service as shown below.<\/span><\/li><\/ol>

                    \"\"<\/p>

                    1. User can check the service in the example section by clicking on the <\/span>Show Live Test Case<\/b> button and click on <\/span>Get Result<\/b> button to get output.<\/span><\/li><\/ol>

                      Steps to configure service Match Junk Value in Marketo:<\/b><\/h3>

                      Please note that the request parameters values (in step 2) and Marketo Fields (in step 4) are just for example. You have to enter the values as per your service requirement.<\/span><\/i><\/p>

                      1. Go to Admin and click Webhooks. Click New Webhook.<\/span><\/p>

                      2. Name and configure your webhook for Service Match Junk Value.<\/span><\/p>

                      \"\"<\/p>

                      Webhook Name:<\/b> Name of the webhook. In the above example, the Webhook name is the same as the Service name. Webhook name can be provided as per requirement.<\/span><\/p>

                      URL:<\/b> The URL of the Service Match Junk Value. The URL has domain and query parameters which will remain the same. You just have to change the parameter values with Marketo Token.\u00a0<\/span><\/p>

                      To insert a token, click Insert Token.<\/span><\/p>

                      Template<\/b>: It will remain blank.<\/span><\/p>

                      Request Token Encoding:<\/b> It will remain None in case of POST, in case of GET field will be uneditable.<\/span><\/p>

                      Response type<\/b>: Select the response format as JSON.<\/span><\/p>

                      Request Type:<\/b> The Request Type will remain the same (i.e) GET as given in the example.<\/span><\/p>

                      1. Add Authentication Header.<\/span><\/li><\/ol>

                        \"\"<\/p>

                        Please note that the auth-key shown above is the original auth-key. So, the same value of auth-key and Content-Type should be used while configuring Webhook as shown.<\/span><\/i><\/p>

                        \"\"<\/p>

                        1. Response Mappings:<\/b> Response Mappings are created via pairing of a Response Attribute. The Response attribute depends on the output you are returning from the Custom service JavaScript function. It is recommended to return JSON from custom service so that you can easily map it with the Marketo field.<\/span><\/li><\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

                          Implementation of RDN Webhook in Marketo In this document, we will learn how to implement the RDN webhook to utilize different services. This example focuses on how to implement RDN services for country and state implementation. Service Name: Match Junk Value Service Type: Advanced Service Service Description: The Junk Lookup service allows users to determine…<\/p>\n","protected":false},"author":47,"featured_media":0,"parent":87157,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"elementor_header_footer","meta":{"footnotes":""},"class_list":["post-87187","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/pages\/87187","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/users\/47"}],"replies":[{"embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/comments?post=87187"}],"version-history":[{"count":7,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/pages\/87187\/revisions"}],"predecessor-version":[{"id":87482,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/pages\/87187\/revisions\/87482"}],"up":[{"embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/pages\/87157"}],"wp:attachment":[{"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/media?parent=87187"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}