Rusty  Shanahan

Rusty Shanahan

1596718560

Principles in Setting Goals for Marketing Programs

We take goals very seriously at Instagram. Goals are important anchors and focus points. They ensure everyone is aligned and set expectations on what a particular marketing program is trying to achieve.

As a Marketing Analytics leader, it is my responsibility to set goals for marketing programs.

However, setting a goal isn’t always easy. Time constraints, complex organizational structures, differing opinions and unclear strategies are some of the many factors that can obscure the goal setting process.

To counter-act these and limit bias, I lean on a set of principles to set goals for each marketing program.

Here are the seven principles I use to allocate goals for Instagram Marketing:

Principle 1: The goal needs to be a natural extension of the business problem, action we want the viewer to take and strategy to achieve that action.

There should be a natural thread from business problem, to action, to strategy and then to the goal. Let’s take a hypothetical example.

The business problem is this — we launched Story Stickers to increase overall content production but users are avoiding the Stickers because they think they are too hard to use.

Action — we want users to try using the stickers and lift overall content production.

Strategy — Use a tutorial based ad to show “non sticker users” an easy way to use a sticker in their Instagram story.

So we’d set our goal around lifting new content production among this selected audience of “non sticker users”.

Principle 2: Each marketing program should have two goals — one sentiment and one product.

The idea here is simple. We want a marketing program to drive both action (as measured by our product goal) and positive sentiment (as measured by our sentiment metric).

If a marketing program delivers on immediate action but not sentiment, then it is not helping us in the long term. If a marketing program lifts sentiment but not action, then it’s not helping us drive immediate business value.

A good measurement program measures many metrics. But there should only be two goals. All other metrics should form part of a learning agenda.

Principle 3: There should be a primary and secondary goal. Success is first judged against the primary goal and then the secondary.

Linked with Principle 2 — Among the two goals, there should be a primary and secondary goal.

Success should be judged against the primary goal first and whether that was achieved. If yes, we move to the second goal. The role of this primary and secondary goal hierarchy is to help prioritize the many go-to-market components.

Principle 4: Goals should be at the top-line, business impact level.

We set top-line goals. What we mean here is that, ultimately, everything we do should move the overall business forward. That might mean adding more users, increasing overall engagement or something.

We need to avoid goals that are too granular. Granular goals don’t tell us if we are moving the business forward, overall.

Returning to our Sticker example from Principle 1. We could set the goal on lifting sticker usage, but that wouldn’t tell us if we’re contributing to the overall business. That’s because the sticker product is ultimately about lifting overall content production, not just sticker usage. A lift in sticker usage may just mean our marketing is cannibalizing another part of the business and not actually raising overall content production and not helping the overall business.

So we set the goal around the overall content production increase.

#marketing-analytics #data-science #marketing #decision-science #analytics #data analytic

What is GEEK

Buddha Community

Principles in Setting Goals for Marketing Programs
Hermann  Frami

Hermann Frami

1651383480

A Simple Wrapper Around Amplify AppSync Simulator

This serverless plugin is a wrapper for amplify-appsync-simulator made for testing AppSync APIs built with serverless-appsync-plugin.

Install

npm install serverless-appsync-simulator
# or
yarn add serverless-appsync-simulator

Usage

This plugin relies on your serverless yml file and on the serverless-offline plugin.

plugins:
  - serverless-dynamodb-local # only if you need dynamodb resolvers and you don't have an external dynamodb
  - serverless-appsync-simulator
  - serverless-offline

Note: Order is important serverless-appsync-simulator must go before serverless-offline

To start the simulator, run the following command:

sls offline start

You should see in the logs something like:

...
Serverless: AppSync endpoint: http://localhost:20002/graphql
Serverless: GraphiQl: http://localhost:20002
...

Configuration

Put options under custom.appsync-simulator in your serverless.yml file

| option | default | description | | ------------------------ | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | | apiKey | 0123456789 | When using API_KEY as authentication type, the key to authenticate to the endpoint. | | port | 20002 | AppSync operations port; if using multiple APIs, the value of this option will be used as a starting point, and each other API will have a port of lastPort + 10 (e.g. 20002, 20012, 20022, etc.) | | wsPort | 20003 | AppSync subscriptions port; if using multiple APIs, the value of this option will be used as a starting point, and each other API will have a port of lastPort + 10 (e.g. 20003, 20013, 20023, etc.) | | location | . (base directory) | Location of the lambda functions handlers. | | refMap | {} | A mapping of resource resolutions for the Ref function | | getAttMap | {} | A mapping of resource resolutions for the GetAtt function | | importValueMap | {} | A mapping of resource resolutions for the ImportValue function | | functions | {} | A mapping of external functions for providing invoke url for external fucntions | | dynamoDb.endpoint | http://localhost:8000 | Dynamodb endpoint. Specify it if you're not using serverless-dynamodb-local. Otherwise, port is taken from dynamodb-local conf | | dynamoDb.region | localhost | Dynamodb region. Specify it if you're connecting to a remote Dynamodb intance. | | dynamoDb.accessKeyId | DEFAULT_ACCESS_KEY | AWS Access Key ID to access DynamoDB | | dynamoDb.secretAccessKey | DEFAULT_SECRET | AWS Secret Key to access DynamoDB | | dynamoDb.sessionToken | DEFAULT_ACCESS_TOKEEN | AWS Session Token to access DynamoDB, only if you have temporary security credentials configured on AWS | | dynamoDb.* | | You can add every configuration accepted by DynamoDB SDK | | rds.dbName | | Name of the database | | rds.dbHost | | Database host | | rds.dbDialect | | Database dialect. Possible values (mysql | postgres) | | rds.dbUsername | | Database username | | rds.dbPassword | | Database password | | rds.dbPort | | Database port | | watch | - *.graphql
- *.vtl | Array of glob patterns to watch for hot-reloading. |

Example:

custom:
  appsync-simulator:
    location: '.webpack/service' # use webpack build directory
    dynamoDb:
      endpoint: 'http://my-custom-dynamo:8000'

Hot-reloading

By default, the simulator will hot-relad when changes to *.graphql or *.vtl files are detected. Changes to *.yml files are not supported (yet? - this is a Serverless Framework limitation). You will need to restart the simulator each time you change yml files.

Hot-reloading relies on watchman. Make sure it is installed on your system.

You can change the files being watched with the watch option, which is then passed to watchman as the match expression.

e.g.

custom:
  appsync-simulator:
    watch:
      - ["match", "handlers/**/*.vtl", "wholename"] # => array is interpreted as the literal match expression
      - "*.graphql"                                 # => string like this is equivalent to `["match", "*.graphql"]`

Or you can opt-out by leaving an empty array or set the option to false

Note: Functions should not require hot-reloading, unless you are using a transpiler or a bundler (such as webpack, babel or typescript), un which case you should delegate hot-reloading to that instead.

Resource CloudFormation functions resolution

This plugin supports some resources resolution from the Ref, Fn::GetAtt and Fn::ImportValue functions in your yaml file. It also supports some other Cfn functions such as Fn::Join, Fb::Sub, etc.

Note: Under the hood, this features relies on the cfn-resolver-lib package. For more info on supported cfn functions, refer to the documentation

Basic usage

You can reference resources in your functions' environment variables (that will be accessible from your lambda functions) or datasource definitions. The plugin will automatically resolve them for you.

provider:
  environment:
    BUCKET_NAME:
      Ref: MyBucket # resolves to `my-bucket-name`

resources:
  Resources:
    MyDbTable:
      Type: AWS::DynamoDB::Table
      Properties:
        TableName: myTable
      ...
    MyBucket:
      Type: AWS::S3::Bucket
      Properties:
        BucketName: my-bucket-name
    ...

# in your appsync config
dataSources:
  - type: AMAZON_DYNAMODB
    name: dynamosource
    config:
      tableName:
        Ref: MyDbTable # resolves to `myTable`

Override (or mock) values

Sometimes, some references cannot be resolved, as they come from an Output from Cloudformation; or you might want to use mocked values in your local environment.

In those cases, you can define (or override) those values using the refMap, getAttMap and importValueMap options.

  • refMap takes a mapping of resource name to value pairs
  • getAttMap takes a mapping of resource name to attribute/values pairs
  • importValueMap takes a mapping of import name to values pairs

Example:

custom:
  appsync-simulator:
    refMap:
      # Override `MyDbTable` resolution from the previous example.
      MyDbTable: 'mock-myTable'
    getAttMap:
      # define ElasticSearchInstance DomainName
      ElasticSearchInstance:
        DomainEndpoint: 'localhost:9200'
    importValueMap:
      other-service-api-url: 'https://other.api.url.com/graphql'

# in your appsync config
dataSources:
  - type: AMAZON_ELASTICSEARCH
    name: elasticsource
    config:
      # endpoint resolves as 'http://localhost:9200'
      endpoint:
        Fn::Join:
          - ''
          - - https://
            - Fn::GetAtt:
                - ElasticSearchInstance
                - DomainEndpoint

Key-value mock notation

In some special cases you will need to use key-value mock nottation. Good example can be case when you need to include serverless stage value (${self:provider.stage}) in the import name.

This notation can be used with all mocks - refMap, getAttMap and importValueMap

provider:
  environment:
    FINISH_ACTIVITY_FUNCTION_ARN:
      Fn::ImportValue: other-service-api-${self:provider.stage}-url

custom:
  serverless-appsync-simulator:
    importValueMap:
      - key: other-service-api-${self:provider.stage}-url
        value: 'https://other.api.url.com/graphql'

Limitations

This plugin only tries to resolve the following parts of the yml tree:

  • provider.environment
  • functions[*].environment
  • custom.appSync

If you have the need of resolving others, feel free to open an issue and explain your use case.

For now, the supported resources to be automatically resovled by Ref: are:

  • DynamoDb tables
  • S3 Buckets

Feel free to open a PR or an issue to extend them as well.

External functions

When a function is not defined withing the current serverless file you can still call it by providing an invoke url which should point to a REST method. Make sure you specify "get" or "post" for the method. Default is "get", but you probably want "post".

custom:
  appsync-simulator:
    functions:
      addUser:
        url: http://localhost:3016/2015-03-31/functions/addUser/invocations
        method: post
      addPost:
        url: https://jsonplaceholder.typicode.com/posts
        method: post

Supported Resolver types

This plugin supports resolvers implemented by amplify-appsync-simulator, as well as custom resolvers.

From Aws Amplify:

  • NONE
  • AWS_LAMBDA
  • AMAZON_DYNAMODB
  • PIPELINE

Implemented by this plugin

  • AMAZON_ELASTIC_SEARCH
  • HTTP
  • RELATIONAL_DATABASE

Relational Database

Sample VTL for a create mutation

#set( $cols = [] )
#set( $vals = [] )
#foreach( $entry in $ctx.args.input.keySet() )
  #set( $regex = "([a-z])([A-Z]+)")
  #set( $replacement = "$1_$2")
  #set( $toSnake = $entry.replaceAll($regex, $replacement).toLowerCase() )
  #set( $discard = $cols.add("$toSnake") )
  #if( $util.isBoolean($ctx.args.input[$entry]) )
      #if( $ctx.args.input[$entry] )
        #set( $discard = $vals.add("1") )
      #else
        #set( $discard = $vals.add("0") )
      #end
  #else
      #set( $discard = $vals.add("'$ctx.args.input[$entry]'") )
  #end
#end
#set( $valStr = $vals.toString().replace("[","(").replace("]",")") )
#set( $colStr = $cols.toString().replace("[","(").replace("]",")") )
#if ( $valStr.substring(0, 1) != '(' )
  #set( $valStr = "($valStr)" )
#end
#if ( $colStr.substring(0, 1) != '(' )
  #set( $colStr = "($colStr)" )
#end
{
  "version": "2018-05-29",
  "statements":   ["INSERT INTO <name-of-table> $colStr VALUES $valStr", "SELECT * FROM    <name-of-table> ORDER BY id DESC LIMIT 1"]
}

Sample VTL for an update mutation

#set( $update = "" )
#set( $equals = "=" )
#foreach( $entry in $ctx.args.input.keySet() )
  #set( $cur = $ctx.args.input[$entry] )
  #set( $regex = "([a-z])([A-Z]+)")
  #set( $replacement = "$1_$2")
  #set( $toSnake = $entry.replaceAll($regex, $replacement).toLowerCase() )
  #if( $util.isBoolean($cur) )
      #if( $cur )
        #set ( $cur = "1" )
      #else
        #set ( $cur = "0" )
      #end
  #end
  #if ( $util.isNullOrEmpty($update) )
      #set($update = "$toSnake$equals'$cur'" )
  #else
      #set($update = "$update,$toSnake$equals'$cur'" )
  #end
#end
{
  "version": "2018-05-29",
  "statements":   ["UPDATE <name-of-table> SET $update WHERE id=$ctx.args.input.id", "SELECT * FROM <name-of-table> WHERE id=$ctx.args.input.id"]
}

Sample resolver for delete mutation

{
  "version": "2018-05-29",
  "statements":   ["UPDATE <name-of-table> set deleted_at=NOW() WHERE id=$ctx.args.id", "SELECT * FROM <name-of-table> WHERE id=$ctx.args.id"]
}

Sample mutation response VTL with support for handling AWSDateTime

#set ( $index = -1)
#set ( $result = $util.parseJson($ctx.result) )
#set ( $meta = $result.sqlStatementResults[1].columnMetadata)
#foreach ($column in $meta)
    #set ($index = $index + 1)
    #if ( $column["typeName"] == "timestamptz" )
        #set ($time = $result["sqlStatementResults"][1]["records"][0][$index]["stringValue"] )
        #set ( $nowEpochMillis = $util.time.parseFormattedToEpochMilliSeconds("$time.substring(0,19)+0000", "yyyy-MM-dd HH:mm:ssZ") )
        #set ( $isoDateTime = $util.time.epochMilliSecondsToISO8601($nowEpochMillis) )
        $util.qr( $result["sqlStatementResults"][1]["records"][0][$index].put("stringValue", "$isoDateTime") )
    #end
#end
#set ( $res = $util.parseJson($util.rds.toJsonString($util.toJson($result)))[1][0] )
#set ( $response = {} )
#foreach($mapKey in $res.keySet())
    #set ( $s = $mapKey.split("_") )
    #set ( $camelCase="" )
    #set ( $isFirst=true )
    #foreach($entry in $s)
        #if ( $isFirst )
          #set ( $first = $entry.substring(0,1) )
        #else
          #set ( $first = $entry.substring(0,1).toUpperCase() )
        #end
        #set ( $isFirst=false )
        #set ( $stringLength = $entry.length() )
        #set ( $remaining = $entry.substring(1, $stringLength) )
        #set ( $camelCase = "$camelCase$first$remaining" )
    #end
    $util.qr( $response.put("$camelCase", $res[$mapKey]) )
#end
$utils.toJson($response)

Using Variable Map

Variable map support is limited and does not differentiate numbers and strings data types, please inject them directly if needed.

Will be escaped properly: null, true, and false values.

{
  "version": "2018-05-29",
  "statements":   [
    "UPDATE <name-of-table> set deleted_at=NOW() WHERE id=:ID",
    "SELECT * FROM <name-of-table> WHERE id=:ID and unix_timestamp > $ctx.args.newerThan"
  ],
  variableMap: {
    ":ID": $ctx.args.id,
##    ":TIMESTAMP": $ctx.args.newerThan -- This will be handled as a string!!!
  }
}

Requires

Author: Serverless-appsync
Source Code: https://github.com/serverless-appsync/serverless-appsync-simulator 
License: MIT License

#serverless #sync #graphql 

Simpliv LLC

Simpliv LLC

1582886905

Career Goal Mapping Course | The Beginner's Guide to Goal Setting | Simpliv

Description
So, here we are again another year, another opportunity to DO more, BE more, HAVE more but lets look back at last year (and the year before, and the year before that) did you or have you managed to achieve any of the goals on your list? Do you even MAKE “lists”, or do you just kind of wait for “life” to happen to you? Has it been ‘happening’ to you in the way that you want?

This course is for all of those people out there who want to make a CHANGE this year! OR who want to make a difference!! Now, ALTHOUGH I keep saying ‘this year’ - this is because this course was created on 1st Jan 2017 but your ‘year’ can begin at any time. 1st June, 1st September, on your birthday it doesn’t really matter. All that matters, is that you MARK THIS DAY as the day that you turned your life around and everything started to look up!

Am I a motivation coach and speaker? No. Am I here to tell you how rubbish you are and to promise that I have the answer to all of life’s mysteries and ills? No. I am simply someone, who believes that LIFE is about CHOICES. We all have 24 hours in a day, and how we choose to SPEND those hours, minutes, seconds is how we came to be in the position that we are in today maybe it was deliberate, or maybe you’ve kind of just wandered and floated up unto this point. What I can assure you, is that this course is all about the science / art of intention and of DELIBERATE CREATION. Together, you and I are going to create the PLAN for the next 12 months ahead. And then I’m going to show you how you break this plan down, right into day-to-day actions, that will take you in the direction that you want to go in.

No more wandering about. No more pontificating. No more pro-procrastinating! No more ‘thinking’ this is all about Doing. Have you ever looked at someone and been envious? I want their life! How to they do that? What are they DOING that I’m not?? Could it be that they have a master plan, that they’re following? Could it be that they have tuned into what they want, and set about going to get it? I remember when I was 16, and one of the first waitiressing jobs I had was with a company called Peoples Network UK. The lady who ran it (Rita) said to me “You have to grab life by the balls Lisa, and shake it for all its got!!!” About 1 month later, she was dead. Tragic drink-driving car accident. But those words never left me. All you’ve got to do it just GRAB LIFE by the balls!!! And I’m proud to say, almost 20 years later. I’m doing just that!

The methodology I’m about to lay out to you was the reason for 2015 being ‘the year of travel’. I went to around 10 countries that year. I set the intention and off I went. 2016 was the year of completion - financial results. This year 2018, will be the year of relationships. Just watch this space. 2018 is numerologically a year of relationships 2 + 0 + 1 + 8 = 11 = 1 + 1 = 2. Look up life path number 2. So, I invite you, my friend and student, to join me on a journey, whereby together, we reflect, and then we set the intention - and make the next 12 months your most successful EVER!

Note - when your life starts to change and everyone wonders what happened to you?? Please share this course with them! Thank-you in advance!

This is not new-age science or mysticism. This is solid, tangible, measureable life-changing material, which you can use over and over again, to get the results you want, and not just dream about.

Who is the target audience?

Progressive people, self-starters, those who want to get somewhere in life - achievers!
Basic knowledge
Student will need a glass of red wine and a nice quiet place for 3-4 hours to seriously think about their life - and where they want it to go
What will you learn
Create and manifest the best ever year of their life - a process they’ll be able to repeat at intervals (annually, monthly, seasonally), and just create the life they know, want and deserve!

ENROLL

#Top Goal Setting Courses Online #Online Goal Setting Classes #Certified Goal Mapping Coach Programme #Goal Setting online short course

Hermann  Frami

Hermann Frami

1651319520

Serverless APIGateway Service Proxy

Serverless APIGateway Service Proxy

This Serverless Framework plugin supports the AWS service proxy integration feature of API Gateway. You can directly connect API Gateway to AWS services without Lambda.

Install

Run serverless plugin install in your Serverless project.

serverless plugin install -n serverless-apigateway-service-proxy

Supported AWS services

Here is a services list which this plugin supports for now. But will expand to other services in the feature. Please pull request if you are intersted in it.

  • Kinesis Streams
  • SQS
  • S3
  • SNS
  • DynamoDB
  • EventBridge

How to use

Define settings of the AWS services you want to integrate under custom > apiGatewayServiceProxies and run serverless deploy.

Kinesis

Sample syntax for Kinesis proxy in serverless.yml.

custom:
  apiGatewayServiceProxies:
    - kinesis: # partitionkey is set apigateway requestid by default
        path: /kinesis
        method: post
        streamName: { Ref: 'YourStream' }
        cors: true
    - kinesis:
        path: /kinesis
        method: post
        partitionKey: 'hardcordedkey' # use static partitionkey
        streamName: { Ref: 'YourStream' }
        cors: true
    - kinesis:
        path: /kinesis/{myKey} # use path parameter
        method: post
        partitionKey:
          pathParam: myKey
        streamName: { Ref: 'YourStream' }
        cors: true
    - kinesis:
        path: /kinesis
        method: post
        partitionKey:
          bodyParam: data.myKey # use body parameter
        streamName: { Ref: 'YourStream' }
        cors: true
    - kinesis:
        path: /kinesis
        method: post
        partitionKey:
          queryStringParam: myKey # use query string param
        streamName: { Ref: 'YourStream' }
        cors: true
    - kinesis: # PutRecords
        path: /kinesis
        method: post
        action: PutRecords
        streamName: { Ref: 'YourStream' }
        cors: true

resources:
  Resources:
    YourStream:
      Type: AWS::Kinesis::Stream
      Properties:
        ShardCount: 1

Sample request after deploying.

curl https://xxxxxxx.execute-api.us-east-1.amazonaws.com/dev/kinesis -d '{"message": "some data"}'  -H 'Content-Type:application/json'

SQS

Sample syntax for SQS proxy in serverless.yml.

custom:
  apiGatewayServiceProxies:
    - sqs:
        path: /sqs
        method: post
        queueName: { 'Fn::GetAtt': ['SQSQueue', 'QueueName'] }
        cors: true

resources:
  Resources:
    SQSQueue:
      Type: 'AWS::SQS::Queue'

Sample request after deploying.

curl https://xxxxxx.execute-api.us-east-1.amazonaws.com/dev/sqs -d '{"message": "testtest"}' -H 'Content-Type:application/json'

Customizing request parameters

If you'd like to pass additional data to the integration request, you can do so by including your custom API Gateway request parameters in serverless.yml like so:

custom:
  apiGatewayServiceProxies:
    - sqs:
        path: /queue
        method: post
        queueName: !GetAtt MyQueue.QueueName
        cors: true

        requestParameters:
          'integration.request.querystring.MessageAttribute.1.Name': "'cognitoIdentityId'"
          'integration.request.querystring.MessageAttribute.1.Value.StringValue': 'context.identity.cognitoIdentityId'
          'integration.request.querystring.MessageAttribute.1.Value.DataType': "'String'"
          'integration.request.querystring.MessageAttribute.2.Name': "'cognitoAuthenticationProvider'"
          'integration.request.querystring.MessageAttribute.2.Value.StringValue': 'context.identity.cognitoAuthenticationProvider'
          'integration.request.querystring.MessageAttribute.2.Value.DataType': "'String'"

The alternative way to pass MessageAttribute parameters is via a request body mapping template.

Customizing request body mapping templates

See the SQS section under Customizing request body mapping templates

Customizing responses

Simplified response template customization

You can get a simple customization of the responses by providing a template for the possible responses. The template is assumed to be application/json.

custom:
  apiGatewayServiceProxies:
    - sqs:
        path: /queue
        method: post
        queueName: !GetAtt MyQueue.QueueName
        cors: true
        response:
          template:
            # `success` is used when the integration response is 200
            success: |-
              { "message: "accepted" }
            # `clientError` is used when the integration response is 400
            clientError: |-
              { "message": "there is an error in your request" }
            # `serverError` is used when the integration response is 500
            serverError: |-
              { "message": "there was an error handling your request" }

Full response customization

If you want more control over the integration response, you can provide an array of objects for the response value:

custom:
  apiGatewayServiceProxies:
    - sqs:
        path: /queue
        method: post
        queueName: !GetAtt MyQueue.QueueName
        cors: true
        response:
          - statusCode: 200
            selectionPattern: '2\\d{2}'
            responseParameters: {}
            responseTemplates:
              application/json: |-
                { "message": "accepted" }

The object keys correspond to the API Gateway integration response object.

S3

Sample syntax for S3 proxy in serverless.yml.

custom:
  apiGatewayServiceProxies:
    - s3:
        path: /s3
        method: post
        action: PutObject
        bucket:
          Ref: S3Bucket
        key: static-key.json # use static key
        cors: true

    - s3:
        path: /s3/{myKey} # use path param
        method: get
        action: GetObject
        bucket:
          Ref: S3Bucket
        key:
          pathParam: myKey
        cors: true

    - s3:
        path: /s3
        method: delete
        action: DeleteObject
        bucket:
          Ref: S3Bucket
        key:
          queryStringParam: key # use query string param
        cors: true

resources:
  Resources:
    S3Bucket:
      Type: 'AWS::S3::Bucket'

Sample request after deploying.

curl https://xxxxxx.execute-api.us-east-1.amazonaws.com/dev/s3 -d '{"message": "testtest"}' -H 'Content-Type:application/json'

Customizing request parameters

Similar to the SQS support, you can customize the default request parameters serverless.yml like so:

custom:
  apiGatewayServiceProxies:
    - s3:
        path: /s3
        method: post
        action: PutObject
        bucket:
          Ref: S3Bucket
        cors: true

        requestParameters:
          # if requestParameters has a 'integration.request.path.object' property you should remove the key setting
          'integration.request.path.object': 'context.requestId'
          'integration.request.header.cache-control': "'public, max-age=31536000, immutable'"

Customizing request templates

If you'd like use custom API Gateway request templates, you can do so like so:

custom:
  apiGatewayServiceProxies:
    - s3:
        path: /s3
        method: get
        action: GetObject
        bucket:
          Ref: S3Bucket
        request:
          template:
            application/json: |
              #set ($specialStuff = $context.request.header.x-special)
              #set ($context.requestOverride.path.object = $specialStuff.replaceAll('_', '-'))
              {}

Note that if the client does not provide a Content-Type header in the request, ApiGateway defaults to application/json.

Customize the Path Override in API Gateway

Added the new customization parameter that lets the user set a custom Path Override in API Gateway other than the {bucket}/{object} This parameter is optional and if not set, will fall back to {bucket}/{object} The Path Override will add {bucket}/ automatically in front

Please keep in mind, that key or path.object still needs to be set at the moment (maybe this will be made optional later on with this)

Usage (With 2 Path Parameters (folder and file and a fixed file extension)):

custom:
  apiGatewayServiceProxies:
    - s3:
        path: /s3/{folder}/{file}
        method: get
        action: GetObject
        pathOverride: '{folder}/{file}.xml'
        bucket:
          Ref: S3Bucket
        cors: true

        requestParameters:
          # if requestParameters has a 'integration.request.path.object' property you should remove the key setting
          'integration.request.path.folder': 'method.request.path.folder'
          'integration.request.path.file': 'method.request.path.file'
          'integration.request.path.object': 'context.requestId'
          'integration.request.header.cache-control': "'public, max-age=31536000, immutable'"

This will result in API Gateway setting the Path Override attribute to {bucket}/{folder}/{file}.xml So for example if you navigate to the API Gatway endpoint /language/en it will fetch the file in S3 from {bucket}/language/en.xml

Can use greedy, for deeper Folders

The forementioned example can also be shortened by a greedy approach. Thanks to @taylorreece for mentioning this.

custom:
  apiGatewayServiceProxies:
    - s3:
        path: /s3/{myPath+}
        method: get
        action: GetObject
        pathOverride: '{myPath}.xml'
        bucket:
          Ref: S3Bucket
        cors: true

        requestParameters:
          # if requestParameters has a 'integration.request.path.object' property you should remove the key setting
          'integration.request.path.myPath': 'method.request.path.myPath'
          'integration.request.path.object': 'context.requestId'
          'integration.request.header.cache-control': "'public, max-age=31536000, immutable'"

This will translate for example /s3/a/b/c to a/b/c.xml

Customizing responses

You can get a simple customization of the responses by providing a template for the possible responses. The template is assumed to be application/json.

custom:
  apiGatewayServiceProxies:
    - s3:
        path: /s3
        method: post
        action: PutObject
        bucket:
          Ref: S3Bucket
        key: static-key.json
        response:
          template:
            # `success` is used when the integration response is 200
            success: |-
              { "message: "accepted" }
            # `clientError` is used when the integration response is 400
            clientError: |-
              { "message": "there is an error in your request" }
            # `serverError` is used when the integration response is 500
            serverError: |-
              { "message": "there was an error handling your request" }

SNS

Sample syntax for SNS proxy in serverless.yml.

custom:
  apiGatewayServiceProxies:
    - sns:
        path: /sns
        method: post
        topicName: { 'Fn::GetAtt': ['SNSTopic', 'TopicName'] }
        cors: true

resources:
  Resources:
    SNSTopic:
      Type: AWS::SNS::Topic

Sample request after deploying.

curl https://xxxxxx.execute-api.us-east-1.amazonaws.com/dev/sns -d '{"message": "testtest"}' -H 'Content-Type:application/json'

Customizing responses

Simplified response template customization

You can get a simple customization of the responses by providing a template for the possible responses. The template is assumed to be application/json.

custom:
  apiGatewayServiceProxies:
    - sns:
        path: /sns
        method: post
        topicName: { 'Fn::GetAtt': ['SNSTopic', 'TopicName'] }
        cors: true
        response:
          template:
            # `success` is used when the integration response is 200
            success: |-
              { "message: "accepted" }
            # `clientError` is used when the integration response is 400
            clientError: |-
              { "message": "there is an error in your request" }
            # `serverError` is used when the integration response is 500
            serverError: |-
              { "message": "there was an error handling your request" }

Full response customization

If you want more control over the integration response, you can provide an array of objects for the response value:

custom:
  apiGatewayServiceProxies:
    - sns:
        path: /sns
        method: post
        topicName: { 'Fn::GetAtt': ['SNSTopic', 'TopicName'] }
        cors: true
        response:
          - statusCode: 200
            selectionPattern: '2\d{2}'
            responseParameters: {}
            responseTemplates:
              application/json: |-
                { "message": "accepted" }

The object keys correspond to the API Gateway integration response object.

Content Handling and Pass Through Behaviour customization

If you want to work with binary fata, you can not specify contentHandling and PassThrough inside the request object.

custom:
  apiGatewayServiceProxies:
    - sns:
        path: /sns
        method: post
        topicName: { 'Fn::GetAtt': ['SNSTopic', 'TopicName'] }
        request:
          contentHandling: CONVERT_TO_TEXT
          passThrough: WHEN_NO_TEMPLATES

The allowed values correspond with the API Gateway Method integration for ContentHandling and PassthroughBehavior

DynamoDB

Sample syntax for DynamoDB proxy in serverless.yml. Currently, the supported DynamoDB Operations are PutItem, GetItem and DeleteItem.

custom:
  apiGatewayServiceProxies:
    - dynamodb:
        path: /dynamodb/{id}/{sort}
        method: put
        tableName: { Ref: 'YourTable' }
        hashKey: # set pathParam or queryStringParam as a partitionkey.
          pathParam: id
          attributeType: S
        rangeKey: # required if also using sort key. set pathParam or queryStringParam.
          pathParam: sort
          attributeType: S
        action: PutItem # specify action to the table what you want
        condition: attribute_not_exists(Id) # optional Condition Expressions parameter for the table
        cors: true
    - dynamodb:
        path: /dynamodb
        method: get
        tableName: { Ref: 'YourTable' }
        hashKey:
          queryStringParam: id # use query string parameter
          attributeType: S
        rangeKey:
          queryStringParam: sort
          attributeType: S
        action: GetItem
        cors: true
    - dynamodb:
        path: /dynamodb/{id}
        method: delete
        tableName: { Ref: 'YourTable' }
        hashKey:
          pathParam: id
          attributeType: S
        action: DeleteItem
        cors: true

resources:
  Resources:
    YourTable:
      Type: AWS::DynamoDB::Table
      Properties:
        TableName: YourTable
        AttributeDefinitions:
          - AttributeName: id
            AttributeType: S
          - AttributeName: sort
            AttributeType: S
        KeySchema:
          - AttributeName: id
            KeyType: HASH
          - AttributeName: sort
            KeyType: RANGE
        ProvisionedThroughput:
          ReadCapacityUnits: 1
          WriteCapacityUnits: 1

Sample request after deploying.

curl -XPUT https://xxxxxxx.execute-api.us-east-1.amazonaws.com/dev/dynamodb/<hashKey>/<sortkey> \
 -d '{"name":{"S":"john"},"address":{"S":"xxxxx"}}' \
 -H 'Content-Type:application/json'

EventBridge

Sample syntax for EventBridge proxy in serverless.yml.

custom:
  apiGatewayServiceProxies:
    - eventbridge:  # source and detailType are hardcoded; detail defaults to POST body
        path: /eventbridge
        method: post
        source: 'hardcoded_source'
        detailType: 'hardcoded_detailType'
        eventBusName: { Ref: 'YourBusName' }
        cors: true
    - eventbridge:  # source and detailType as path parameters
        path: /eventbridge/{detailTypeKey}/{sourceKey}
        method: post
        detailType:
          pathParam: detailTypeKey
        source:
          pathParam: sourceKey
        eventBusName: { Ref: 'YourBusName' }
        cors: true
    - eventbridge:  # source, detail, and detailType as body parameters
        path: /eventbridge/{detailTypeKey}/{sourceKey}
        method: post
        detailType:
          bodyParam: data.detailType
        source:
          bodyParam: data.source
        detail:
          bodyParam: data.detail
        eventBusName: { Ref: 'YourBusName' }
        cors: true

resources:
  Resources:
    YourBus:
      Type: AWS::Events::EventBus
      Properties:
        Name: YourEventBus

Sample request after deploying.

curl https://xxxxxxx.execute-api.us-east-1.amazonaws.com/dev/eventbridge -d '{"message": "some data"}'  -H 'Content-Type:application/json'

Common API Gateway features

Enabling CORS

To set CORS configurations for your HTTP endpoints, simply modify your event configurations as follows:

custom:
  apiGatewayServiceProxies:
    - kinesis:
        path: /kinesis
        method: post
        streamName: { Ref: 'YourStream' }
        cors: true

Setting cors to true assumes a default configuration which is equivalent to:

custom:
  apiGatewayServiceProxies:
    - kinesis:
        path: /kinesis
        method: post
        streamName: { Ref: 'YourStream' }
        cors:
          origin: '*'
          headers:
            - Content-Type
            - X-Amz-Date
            - Authorization
            - X-Api-Key
            - X-Amz-Security-Token
            - X-Amz-User-Agent
          allowCredentials: false

Configuring the cors property sets Access-Control-Allow-Origin, Access-Control-Allow-Headers, Access-Control-Allow-Methods,Access-Control-Allow-Credentials headers in the CORS preflight response. To enable the Access-Control-Max-Age preflight response header, set the maxAge property in the cors object:

custom:
  apiGatewayServiceProxies:
    - kinesis:
        path: /kinesis
        method: post
        streamName: { Ref: 'YourStream' }
        cors:
          origin: '*'
          maxAge: 86400

If you are using CloudFront or another CDN for your API Gateway, you may want to setup a Cache-Control header to allow for OPTIONS request to be cached to avoid the additional hop.

To enable the Cache-Control header on preflight response, set the cacheControl property in the cors object:

custom:
  apiGatewayServiceProxies:
    - kinesis:
        path: /kinesis
        method: post
        streamName: { Ref: 'YourStream' }
        cors:
          origin: '*'
          headers:
            - Content-Type
            - X-Amz-Date
            - Authorization
            - X-Api-Key
            - X-Amz-Security-Token
            - X-Amz-User-Agent
          allowCredentials: false
          cacheControl: 'max-age=600, s-maxage=600, proxy-revalidate' # Caches on browser and proxy for 10 minutes and doesnt allow proxy to serve out of date content

Adding Authorization

You can pass in any supported authorization type:

custom:
  apiGatewayServiceProxies:
    - sqs:
        path: /sqs
        method: post
        queueName: { 'Fn::GetAtt': ['SQSQueue', 'QueueName'] }
        cors: true

        # optional - defaults to 'NONE'
        authorizationType: 'AWS_IAM' # can be one of ['NONE', 'AWS_IAM', 'CUSTOM', 'COGNITO_USER_POOLS']

        # when using 'CUSTOM' authorization type, one should specify authorizerId
        # authorizerId: { Ref: 'AuthorizerLogicalId' }
        # when using 'COGNITO_USER_POOLS' authorization type, one can specify a list of authorization scopes
        # authorizationScopes: ['scope1','scope2']

resources:
  Resources:
    SQSQueue:
      Type: 'AWS::SQS::Queue'

Source: AWS::ApiGateway::Method docs

Enabling API Token Authentication

You can indicate whether the method requires clients to submit a valid API key using private flag:

custom:
  apiGatewayServiceProxies:
    - sqs:
        path: /sqs
        method: post
        queueName: { 'Fn::GetAtt': ['SQSQueue', 'QueueName'] }
        cors: true
        private: true

resources:
  Resources:
    SQSQueue:
      Type: 'AWS::SQS::Queue'

which is the same syntax used in Serverless framework.

Source: Serverless: Setting API keys for your Rest API

Source: AWS::ApiGateway::Method docs

Using a Custom IAM Role

By default, the plugin will generate a role with the required permissions for each service type that is configured.

You can configure your own role by setting the roleArn attribute:

custom:
  apiGatewayServiceProxies:
    - sqs:
        path: /sqs
        method: post
        queueName: { 'Fn::GetAtt': ['SQSQueue', 'QueueName'] }
        cors: true
        roleArn: # Optional. A default role is created when not configured
          Fn::GetAtt: [CustomS3Role, Arn]

resources:
  Resources:
    SQSQueue:
      Type: 'AWS::SQS::Queue'
    CustomS3Role:
      # Custom Role definition
      Type: 'AWS::IAM::Role'

Customizing API Gateway parameters

The plugin allows one to specify which parameters the API Gateway method accepts.

A common use case is to pass custom data to the integration request:

custom:
  apiGatewayServiceProxies:
    - sqs:
        path: /sqs
        method: post
        queueName: { 'Fn::GetAtt': ['SqsQueue', 'QueueName'] }
        cors: true
        acceptParameters:
          'method.request.header.Custom-Header': true
        requestParameters:
          'integration.request.querystring.MessageAttribute.1.Name': "'custom-Header'"
          'integration.request.querystring.MessageAttribute.1.Value.StringValue': 'method.request.header.Custom-Header'
          'integration.request.querystring.MessageAttribute.1.Value.DataType': "'String'"
resources:
  Resources:
    SqsQueue:
      Type: 'AWS::SQS::Queue'

Any published SQS message will have the Custom-Header value added as a message attribute.

Customizing request body mapping templates

Kinesis

If you'd like to add content types or customize the default templates, you can do so by including your custom API Gateway request mapping template in serverless.yml like so:

# Required for using Fn::Sub
plugins:
  - serverless-cloudformation-sub-variables

custom:
  apiGatewayServiceProxies:
    - kinesis:
        path: /kinesis
        method: post
        streamName: { Ref: 'MyStream' }
        request:
          template:
            text/plain:
              Fn::Sub:
                - |
                  #set($msgBody = $util.parseJson($input.body))
                  #set($msgId = $msgBody.MessageId)
                  {
                      "Data": "$util.base64Encode($input.body)",
                      "PartitionKey": "$msgId",
                      "StreamName": "#{MyStreamArn}"
                  }
                - MyStreamArn:
                    Fn::GetAtt: [MyStream, Arn]

It is important that the mapping template will return a valid application/json string

Source: How to connect SNS to Kinesis for cross-account delivery via API Gateway

SQS

Customizing SQS request templates requires us to force all requests to use an application/x-www-form-urlencoded style body. The plugin sets the Content-Type header to application/x-www-form-urlencoded for you, but API Gateway will still look for the template under the application/json request template type, so that is where you need to configure you request body in serverless.yml:

custom:
  apiGatewayServiceProxies:
    - sqs:
        path: /{version}/event/receiver
        method: post
        queueName: { 'Fn::GetAtt': ['SqsQueue', 'QueueName'] }
        request:
          template:
            application/json: |-
              #set ($body = $util.parseJson($input.body))
              Action=SendMessage##
              &MessageGroupId=$util.urlEncode($body.event_type)##
              &MessageDeduplicationId=$util.urlEncode($body.event_id)##
              &MessageAttribute.1.Name=$util.urlEncode("X-Custom-Signature")##
              &MessageAttribute.1.Value.DataType=String##
              &MessageAttribute.1.Value.StringValue=$util.urlEncode($input.params("X-Custom-Signature"))##
              &MessageBody=$util.urlEncode($input.body)

Note that the ## at the end of each line is an empty comment. In VTL this has the effect of stripping the newline from the end of the line (as it is commented out), which makes API Gateway read all the lines in the template as one line.

Be careful when mixing additional requestParameters into your SQS endpoint as you may overwrite the integration.request.header.Content-Type and stop the request template from being parsed correctly. You may also unintentionally create conflicts between parameters passed using requestParameters and those in your request template. Typically you should only use the request template if you need to manipulate the incoming request body in some way.

Your custom template must also set the Action and MessageBody parameters, as these will not be added for you by the plugin.

When using a custom request body, headers sent by a client will no longer be passed through to the SQS queue (PassthroughBehavior is automatically set to NEVER). You will need to pass through headers sent by the client explicitly in the request body. Also, any custom querystring parameters in the requestParameters array will be ignored. These also need to be added via the custom request body.

SNS

Similar to the Kinesis support, you can customize the default request mapping templates in serverless.yml like so:

# Required for using Fn::Sub
plugins:
  - serverless-cloudformation-sub-variables

custom:
  apiGatewayServiceProxies:
    - kinesis:
        path: /sns
        method: post
        topicName: { 'Fn::GetAtt': ['SNSTopic', 'TopicName'] }
        request:
          template:
            application/json:
              Fn::Sub:
                - "Action=Publish&Message=$util.urlEncode('This is a fixed message')&TopicArn=$util.urlEncode('#{MyTopicArn}')"
                - MyTopicArn: { Ref: MyTopic }

It is important that the mapping template will return a valid application/x-www-form-urlencoded string

Source: Connect AWS API Gateway directly to SNS using a service integration

Custom response body mapping templates

You can customize the response body by providing mapping templates for success, server errors (5xx) and client errors (4xx).

Templates must be in JSON format. If a template isn't provided, the integration response will be returned as-is to the client.

Kinesis Example

custom:
  apiGatewayServiceProxies:
    - kinesis:
        path: /kinesis
        method: post
        streamName: { Ref: 'MyStream' }
        response:
          template:
            success: |
              {
                "success": true
              }
            serverError: |
              {
                "success": false,
                "errorMessage": "Server Error"
              }
            clientError: |
              {
                "success": false,
                "errorMessage": "Client Error"
              }

Author: Serverless-operations
Source Code: https://github.com/serverless-operations/serverless-apigateway-service-proxy 
License: 

#serverless #api #aws 

Aria Lee

Aria Lee

1609507876

25 Best Digital Marketers In India | Best Digital Marketing Experts In India

The demand for digital marketing is increasing. This in turn is increasing the demand for digital marketing experts in India. There are many digital marketers in India.
This blog post lists the best 25 digital marketing experts in India who have outstanding work in the digital marketing field.

But, according to the 25** best digital marketing experts**, there exists a simple way to find out what is working in this market.

Today, I do not think any business can survive without digital marketing. You know that digital marketing talent is rare. You should check the results of our digital marketing talent survey. Here, we have compiled a list of 25 best digital marketers in India.

1. SEO Vaibhav Sharma

Vaibhav Sharma (Born 28-07-1998), better known as SEO Vaibhav Sharma, Youngest Digital Marketing Expert and Blogger and youtube personality since 2017. Work As Freelancer SEO Expert | SMO Expert | PPC Expert. He Is Also Known for his hard & Smart work in the Digital Marketing Industry.
They served their digital marketing services for international and also domestic clients and they all are happy with them.
Vaibhav Sharma is Google Certified Digital Marketer and he helps businesses to achieve their goals.
Experties In: Local SEO, Lead Generation, Branding, etc…

You can contact Vaibhav Sharma through mail: vaibhavsharmaseo@gmail.com
Website: https://seovaibhavsharma.com

2. Sorav Jain

After embarking on the SEO journey in his early 17s, Sorav Jain made significant contributions to the digital marketing industry. He is the CEO of Echo, a self-funded firm that provides world-class social media and digital marketing expertise.

Website: https://www.soravjain.com/

3. Mridul Kabra

By graduating as an architect, he is the first student of Malaviya National Institute of Technology to become a teacher and digital marketing expert. He is also working as google certified Digital Marketer expertise in lead generation.

4. Jitendra Vaswani

Jitendra Vaswani is a professional digital marketer and blogger, currently based out of India. His blog, BloggersIdeas, is one of the top ranking blogs on blogging and digital marketing in the country. He is also a top digital marketing consultant in India, a public speaker and has spoken at events, colleges and forums in India, blogging, personal branding and keynote making online.

5. Prateek Shah

Prateek is a best digital marketing trainer with Google India and head trainer of AIMA (All India Management Association). Apart from managing social media campaigns for various brands, he launched India’s first student social network ‘Asset Ambassador’.

He founded Digital Defined in October 2015, with the aim of creating a platform for digital marketing professionals and enthusiasts. It is a digital marketing hub for communicating, contributing and collaborating digital marketing ideas and receiving all marketing questions.

6. Deepak Kanakaraju

Deepak Kanakaraju is famous in the world of digital marketing as Digital Deepak. His blog digitaldeepak.com is an amazing resource for those who want to learn digital marketing.
Deepak loves bikes and started a blog on a motorcycle called BikeAdvice which got more than 1 lakh followers and 1 million plus page views per month. This was his debut in digital marketing.
Following this bike blog, Deepak worked in several companies and also spoke on digital marketing. The blog DigitalDeepak.com has been ranked as one of the top 10 digital marketing blogs in India.

7. Pradeep Chopra

Pradeep Chopra is an IIT Delhi pass out. He is one of the pioneers of digital marketing in India. Pradeep is the co-founder and CEO of Digital Vidya. He is an author on International Fence and Digital Marketing and Entrepreneurship.
Pradeep has organized several social media workshops in India at Singapore, Click Asia Summit, Tycon, Global Youth Marketing Force and NASSCOM India Leadership Force.
He has trained and mentored thousands of professionals and CEOs in digital marketing. Pradeep believes “Internet connectivity is more important than water supply”

8. Ankit Malik

Over 7 years of agency and in-house experience in digital marketing. Ankit Malik is capable of managing and executing projects of any size and budget. Ankit Malik owns brands like HBO India, Yatra, Lufthansa, Mercedes, Intel and many more. Ankit Malik is considered the best in the social media industry and was also nominated in the top 30 under 30 social media and brand markets in 2018. Ankit has previously worked with MRM MCCAN and India’s most luxury hospital Roswalk Healthcare. His expertise lies in the medical and entertainment section. Ankit also won the ‘Top 200 Movie Blogs 2018’ awarded by FeedSpot and is currently working with renowned brands in India and Canada.

9. Ananthanarayanan V

PGCPM from Indian Institute of Management in Indore in 2007. Also awarded the “Best Digital Advertising Professionals in India” from the CMO Council and World Advertising Congress from the fourth edition of “50 Best Digital Marketing Professionals, 2014” at the “Mobile and Digital Marketing Summit 2014” held at TAJ Scandal END, MUMBAI . 14 November 2014. The theme of the summit is “Real-time through mobile and digital media: real-time marketing and engagement”. Organization: He is the founder and CEO of TechDivine Creative Services based in Thane West, Mumbai, Maharashtra, India.

10. Himanshu Arora

The co-founder of Socialpanga, Himanshu Arora, believes in deep electronic marketing. Being an expert in designing, strategizing and implementing electronic marketing through various strategies and campaigns, he represents himself as a ‘marketing mafia’. He has worked with around 50 firms, including Coca-Cola, SAP, Google, Accenture, Horricks, and more. In addition, he has been selected as the Google Award for Google Product and Sales Award. Himanshu is a renowned speaker and has conducted more than 35 electronic advertising and marketing training sessions for notable firms such as Kodak, Nokia, Wipro, and many more.

11. Aditya Gupta

In 2011, he founded Social Samosa with Ankitagba. His plan was to become a hub for the Indian social media industry by satisfying all earlier knowledge gaps. In 2015, it was sold to confidential investors for an undisclosed sum. According to an ET report, a group of investors bought the company for Rs.2-3 Cr. Now, Ankit works at his digital communications agency Igenero. He founded the company in 2009 with the objective of providing solutions for branding, web-based products and digital strategy on one platform. He has worked with well-known companies.

12. Jainendra singh

He is a Google certified digital marketer in india. His extensive experience in strategic planning and business structure has helped billions of dollars of companies in many industries. For so many years, they have been occupied in measuring the ROI of digital media activities, lead generation and content delivery through popular social and bookmark channels.

13. Laxmipati bhat

With 25 years of experience in the world of marketing, he blends traditional advertising methods and new digital information in a great way. Currently, he is the head of business communications for Robosoft Technologies, a leading mobility solutions partner. He worked with a successful track record in business development in Mumbai, Bangladesh, Sri Lanka and Bangalore with demand for FMCG and service brands and leadership agency profit centers. He worked with P&G, BAT, GSK, Sara Lee, Wipro Consumer Care & Lighting and ITC Foods.

14. Prashant Naidu

Moving on to start LI with his wife, Prashant worked as a business analyst in Singapore, India and the UK for six years.
Prashant Naidu is the founder of a four-and-a-half-year-old young online publishing start-up that covers social media marketing stories beyond press releases. LI has been listed in the Top 10 Social Media Blogs 2013 by Social Media Examiner and Indi Blogger. They believe that high quality content always stays and pays

15. Rajat Jain

Rajat Jain is the founder and CEO of “Shoot Order”, a top-ranked digital marketing company with over 200 customers worldwide. Along with this, he is also considered as the best digital marketing consultant in India. Rajat also writes a blog called “SpeakRJ”, where he shares his marketing experiences and latest developments in the market.

16. Harsh Agarwal

Harsh Agarwal is a B.tech graduate and professional blogger. He has also worked at Convergys before becoming a full-time blogger. His blog “ShoutMeLoud” is a one-stop solution for every aspiring blogger out there. Blogging is a very important and important aspect of Digital Marketing. His expertise in blogging and contribution in this field is excellent.

17. Kunal Chaudhary

Kunal Chaudhary is the founder of Delhi School of Internet Marketing, a renowned digital marketing institute. He has 8+ years of digital marketing experience and has done internet marketing for top brands like Snapdeal, Myntra, Flipkart, FashionAndieu, Jabong etc. He is also a digital marketing specialist with over $ 2 million earned in revenue.

18. Rohit Onkar

Rohit Onkar is One of the best Digital Marketer, Business Leader and Trainer. Rohit has been able to successfully establish scale processes, manage cross-functional teams, increase the profitability of organizations and drive them to desired goals. He is the Head of Digital at Loylty Rewardz Mngt Pvt Ltd, where his role is to oversee daily digital marketing campaigns, set up large-scale processes, identify new monetization opportunities to create new revenue streams and drive daily campaign execution. Have to manage for. A cross-functional team. .

19. Anoop Mishra

Anoop Mishra is a digital marketing specialist. He is the co-founder of Prachar Mantra. Anoop has done BCA, MCA and MBA (Marketing)
He has helped many businesses do digital marketing effectively and efficiently. You can learn more about them at: https://www.anoopmishra.com

20. Suresh Babu

Suresh Babu is the founder and CEO of Web Marketing Academy. He is one of the best digital marketing trainers in India. Suresh holds an Executive MBA from IIMB.
He started his career as a lecturer for Hotel Management and Catering Science and today he is one of the best teachers of digital marketing.
Suresh is a visiting faculty and president at prominent universities like Christ University, Acharya B-School, Commits College, Manetti Community College. He also founded the online marketing enthusiast community, a community of passionate online marketing enthusiasts.

21. Arockiasamy Satya

This B2B marketing professional has contributed to transform the business through appropriate marketing and content strategy. He demonstrates expertise in the planning, construction, implementation, monitoring and analysis of marketing initiatives. When it comes to content writing, the different times with writing different marketing-related articles are true. The two most important business changes he made were in Brillio and Collabera. In addition, he has teamed up with Dell.

22. Chetan Deshpande

Chetan Deshpande is the CEO of Next Level Marketers. Next Level Marketers is a group of experts that takes your marketing and business development to the next level.
He has more than 10 years of experience in digital marketing and is a specialist in implementing and executing inbound marketing. Chetan is very active in the field of digital marketing and has also received many media coverage.

23. Prabhakar Alok

This youngest entrepreneur from Bihar, India, is a digital marketing expert and famous for trends in his city. Prabhakar Alok is the founder of 3 start-ups - DigiwaleBabu, My22yards and DigitalGucucool. Through this, he renders digital marketing services for start-ups across India. DigiwaleBabu is a marketing tool box that provides best-in-class services to its customers in all aspects of online marketing. Apart from being a Google certified digital marketer in India, Prabhakar Alok is a social activist and a star cricketer in his field.

24. Viren Patel

Viren Patel is a co-founder and mentor at Lavenir Institute of Professional Studies.
He has an MBA in Information Management from Somaiya Institute of Management and Research and has 10 years of experience in the web.
His institute Lavenir Institute of Professional Studies is training many people in digital marketing and growing at a great pace.

25. Ashok Lalla

Ashok Lalla is a best digital marketing expert in mumbai. He did his MBA in Marketing from JBIMS, Mumbai.
Ashok was Global Head - Digital Marketing at Infosys from 2012 to 2015. He has worked with many other large companies.
Ashok has a lot of knowledge and expertise in digital marketing. You can learn more about him - www.linkedin.com/in/ashoklalla

Conclusion:

This was a list of the best digital marketers in India I was able to come up with.
Digital marketing is a very dynamic field and to specialize in digital marketing, one has to keep himself updated with the latest trends in digital marketing.

In addition, many of the digital marketing experts listed above provide free guidance to digital marketing enthusiasts. Students without any selfishness and helping the digital marketing community are impacting lives not only in India but around the world.
Obviously I have missed a lot of great minds that I do not know, and I am sorry to miss them!

If you know other great marketers in India, I love to know his name and his work in digital marketing. Leave them in the comments below!

#digital marketer #digital marketing expert #digital marketer in india #digital marketing expert in india #best digital marketer in india #best digital marketing expert in india

Dental SEO Marketing | Dentists SEO Marketing

Medibrandox is the largest company for marketing that provides SEO marketing for dentists and dental clinics and it is a practice of increasing website traffic of quality and quantity both. Dental SEO marketing works by optimizing your site for the search engine that helps to boost your website rank in Google as well as you get a lot of traffic of dentists related. If you are looking dental SEO marketing agency so you should go over the website.

#seo marketing for dentists #seo marketing dental clinics #dental seo marketing company #best dental seo marketing agency #seo marketing for dental clinic #dental seo marketing agency